Jump to content
KAZOOcon: hackathon signup and details here! ×

SPC-Tim

Moderators
  • Posts

    100
  • Joined

  • Days Won

    5

Posts posted by SPC-Tim

  1. 3 hours ago, DinkyDonkey said:

    On Yealinks this is what I'm seeing, "If you go change the provisioning URL under Advanced Provisioner, this will change it for any new devices or factory resets, however existing devices will continue to use the old provisioning URL."

    Without doing a factory reset I don't see how to change the provisioning URL. Do I have to do an unlock on the phone first?

    Yes, You will have to unlock the device, and change the url within the phone.

  2. @anir

    If you are using the Advanced provisioner and are on Hosted or "private cloud" then the Configuration files are on the 2600hz side.

     

    I believe they can only be changed on the account level because many people use the provisioner and the devs put in the default configs to allow for a device to pull down the minimum it needs to work.

     

    On the flip side of this you could write you own config file and have the devices download the config via the custom config URL within Advanced Provisioner

  3. When using call center basic, and have 1 user in multiple queues, Can we add the option of which queue to sign into?

     

    Example is a Manager who is monitoring 3 queues, needs to take calls in one queue but not the other 2 can this happen without having multiple users on one device?

  4. @mds
     

    Yealink does have the ability to add expansion boards with BLF capabilities, and you can provision the keys within the advanced provisioner to use BLF. We have dozens of clients using a T48S with 2 EXP40 Expansion boards and the BLF's programmed this way..

    If you have any questions on setting this up let me know. I will get you some screenshots of the setup.. The actual expansion boards can be found on amazon at https://www.amazon.co.uk/Yealink-EXP40-Expansion-Module-Black/dp/B00JVSKMX2/ref=sr_1_1?ie=UTF8&qid=1518645924&sr=8-1&keywords=exp40

    (That UK link should be good if not just look up EXP40 on amazon.)

  5. Hey Everyone,

    I have had a few customers complaining that Panasonic Phones are not ringing or receiving calls sent to them when the phone is dialed.

    We are on the Hosted side of things.

    I've done a large amount of testing and wanted to share with you what I have found so far:

    I Manually provisioned the device
    Set the device to TCP
    set a static ip address and custom dns to google dns 8.8.8.8 8.8.4.4
    Moved the device to a different network, made the same changes and it still has the same errors
    Connected the phone directly to a modem, and was able to replicate the trouble.
    changed the Jitter Buffer settings to a Maximum delay of 50 and then ran through numerous amounts of tests with ranges all the way to 3
    Changed the Codec Settings to PCMU, G711, G722, and PCMA numerous calls, still ran into issues with calls failing.
    When attempting to get a packet capture of the error, the calls are not even hitting the device to capture the packets
    The device remains registered and can make outbound calls while this is happening.
    tested the same settings in Firmware 12.84, 12.90, and 13.33
     

    The errors are also inconsistent: 
    Unallocated number
    Recovery on timer expire

     

    The device will receive calls after rebooting the device for 1-3 calls, but will then begin failing with the errors you see.

    Any insight you can provide would be helpful!

  6. 3 minutes ago, amn said:

    Keep in mind that removing the ability from the UI does not remove the ability from the API.  Anyone who has access to the UI will also have full access to the API.   So it is better to try restrict it via the API using token restrictions.  Not sure if that is possible or not in token restrictions.

    https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/token_restrictions.md

     

    1

    @amn

    General users don't really know much about API stuff, but the insight is appreciated. Removing it from the UI or seeing if I can lock it out in token may be an option I will investigate it further, But removing the BUY link is the desired solution

     

×
×
  • Create New...