Jump to content

Logicwrath

Customers
  • Posts

    578
  • Joined

  • Days Won

    21

Posts posted by Logicwrath

  1. Hello,

    I have a specific client interested in using SRTP to encrypt voice calls.  I am trying to test these features out but I am running into some issues.  Here is what I have done so far on my Yealink T46S.

    1. Edited device in advanced call flows.  Under the Audio tab I set Secure RTP to SRTP.  This erases your advanced provisioner profile for the device. :(

    2. In the Advanced Provisioner under Lines I made sure that RTP Encryption (SRTP) was set to Enabled.

    3. In the Advanced Provisioner under Lines I made sure that the Primary Address was set to secure-us-east.p.zswitch.net.

    4. In the phones web interface under Account -> Advanced I manually set RTP Encryption (SRTP) to "Compulsory".  I was not able to place outbound calls without setting this manually.

     

    I am able to place outbound calls and lock shows up on my Yealink phone indicating that the call is encrypted.  However, I am seeing some major issues and I was hoping to get some assistance.

    1. BLF is not working.  The BLF keys are showing a RED X.

    2. I am not able to receive inbound calls.  The Hangup Cause is "RECOVERY_ON_TIMER_EXPIRE" with a hangup code of "sip:408"

     

    Any suggestions on how I could get this working?  

  2. Today 1/19/18 I am noticing call audio issues on both EAST and CENTRAL proxies.  I thought maybe it was my Internet connection but I am not able to identify any packet loss or latency issues and my queues are not full or near capacity.

    If I call a call flow that plays audio I am not hearing any major issues.  I usually test for packet loss and audio issues like this by playing a sine wave tone and listen for breaks in the audio.  It appears that the audio coming from the call flow is fine.

    I also noticed that over the last 2 days I have had 2 calls where the callee was unable to hear my audio.  One way audio is typically a NAT issue or networking problem.  However, I don't think this is the case here.  I originally thought maybe it was an issue my PC or headset since I am using Bria but now that we are having consistent audio issues on the PSTN I wanted to post it in case it is related.

    I am wondering if we are having issues with a termination provider being used on the hosted platform.  It appears that inbound calls are working fine.  I suspect this is a termination issue.

  3. Hello,

    Thank you for the example.  I already have a favorite_setting.xml file created, working, and hosted.  The issue is that some of the phones do not allow us to specify a custom config URL to use it in advanced provisioner.  The field is is only available for the some models.

    I just checked the config created by Advanced Provisioner for a T27G phone.  The firmware.url is blank.

    ###The default value is blank.It takes effect after a reboot.
    firmware.url =
    

    I checked another T29G config and it is blank there too.  I think it is always blank in the config files created by advanced provisioner yet they still update/downgrade usually.

  4. Hello,

    We started using the Custom Config URL on the Yealink phones so we can specify that the Remote Phone Book is available under the directory soft key.  It seems like some of the models (T46G, T27G) are supporting this.  The T23G and the T29G do not have a field to configure this Custom Config URL.  However, they do have the same firmware available to it (V81.0.110) as the T27G for example.

    I was hoping that you would be willing to add the Custom Config URL to these phone models.  We want to standardize a remote phone book to all phones showing feature codes and descriptions.  Additionally, using a remote phone book is much harder without having it available in the default Directory soft key.

  5. I suspect that the forum email notifications are no longer getting sent.  I am not seeing any reply notifications or new thread notifications.  I spoke with someone else who said they are no longer getting daily reports.

    I do not see anything in my junk mail folder either.

  6. I am trying to figure out why in some cases we are randomly having phones with incompatible codecs.  Everything will be fine and then one day we get a call that none of the phones are working/ringing.  I will investigate and see a codec incompatibility.  There was a time when I setup a devices to only allow G722.  I don't do this anymore, I include G711 as well.  However, I don't know why the Yealink phone will all of sudden be configured for G711 only.  The issue ends up being that the Yealink phone will be configured for PCMU only and the account will be configured for G722 only.

    I check the Advanced Provisioner CFG file in a web browser and it looks correct:

    account.1.codec.6.enable = 1 account.1.codec.6.priority = 1
    account.1.codec.1.enable = 1 account.1.codec.1.priority = 2

    However, when I log into the Yealink phone it will be set to PCMU only.  The quick fix is to edit the device and allow PCMU so the phones will work.

    Does anyone have any idea why the Yealink phone configuration would suddenly change the codec configuration?  This is rather frustrating.

×
×
  • Create New...