Re: One way voice on SIP Trunk call pickup from another phone.

Douglas Yoder · ‎04-28-2011

Customer is reporting one way voice when SIP trunk calls are picked up from another non ringing extension since phone firmware upgrade. Any ideas why that would be?

CUE 2.3

CME 4.2

David Trad · ‎04-28-2011

Hi Douglas,

Could potentially be a transcoding issue, are all your DSP resources in order??

Have you considered upgrading the IOS and CUE to the latest versions?? You can do this still even thought you might be only maintaining this via CLI, or if you are brave you can rebuild the entire system with CCA and upgraded the entire system to the latest distributed software pack, configuring this kind of stuff is a breeze with CCA and you tend to not come across these types of issues often.

On the router if you run the command ROUTER#sh dsp all

This will show us what is being used up, but if you post your running configuration with all the sensitive data such as user/pass removed and any names, then we can also look at your configuration to see if anything sticks out.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

Douglas Yoder · ‎04-29-2011

Not sure what you mean by "all my DSP resources in order" and yes, I have considered upgrading the IOS and CUE to the latest versions if that will fix the issue. I'm afraid it just make things worse. Thanks for taking a look at this.

sh dsp all n config.txt attached

-Doug

Douglas Yoder · ‎05-19-2011

David,

Did you see anything in the configuration that might be the cause of my issue?

Thanks,

Doug

David Trad · ‎05-19-2011

Hi Douglas,

I can only right now honestly and profusely apologies to you... This one has totally fallen between the cracks and NO I have not looked at this one further...

I have made it a priority to look at this for you today...

Again my deepest apologies, I rarely let any commitments or promises slip.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

David Trad · ‎05-19-2011

Hi Douglas,

Lets start with this first... I hope you can do some CLI work, if not then we may need to look at some remote support.

These may or may not resolve the problem, however we need to do some power of elimination and just some standard diagnosis work first, a little bit of a pain in the backside, but worth it.

Firstly the "124-11.XW7" train had quite a few issues if memory serves me right, I think this is the one almost straight after the first release of the UC-500, regardless it is seriously old and I do not think they had full or proper support for SIP anyway.

Assuming that your current IOS can accept the following commands, you should look at making the following changes.

*******CAUTION******PLEASE MAKE A BACKUP OF YOUR CONFIGURATION BEFORE APPLYING THESE CHANGES********

Update your Voice Class Codecs to resemble the following:

voice class codec 1
 codec preference 1 g729br8
 codec preference 2 g729r8
 codec preference 3 g711ulaw
 codec preference 4 g711alaw

Update your SIP-UA to look like this:

 sip-ua
 credentials username XXXXXXXX password 7 091A772C4C513A395D realm sip.XXXXXXXXX.com
 authentication username XXXXXXXX password 7 040D32235A7561655F
 no remote-party-id
 retry invite 2
 retry register 10
 timers connect 100
 registrar dns:sip.XXXXXXXX.com expires 3600
 sip-server dns:XXX.XXX.XXX.XXX
 connection-reuse
 host-registrar

Consider updating your "Voice Service VoIP" section as well:

sip
  registrar server expires max 3600 min 3600
  localhost dns:sip.XXXXXXXXX.com
   outbound-proxy dns:sip.XXXXXX.com
  no update-callerid

Again, I cannot encourage you enough to do an IOS upgrade, you really need to bring it up to-date if you can to capture the benefits of a more current IOS, you do not have to get the latest one, but at least something just before the 15.X train that has better support for SIP.

Your problem is an audio path issue, the problem is going to be when we do a debug on the ccsip or the capi, what information we can capture, but we will cross that bridge when we get there I guess.

Please look at making the changes if you can.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

mtempro · ‎05-19-2011

Hi Douglas,

I agree with David 100%. As an STAC engineer the first thing I recommend to partners is to upgrade the factory default IOS. Version 12.4 has been through so many revisions that even if an upgrade doesn't address this particular issue, it'll most likely fix a few others that haven't manifested themselves as yet, so it's best to be proactive. Also, I've personally seen sip related issues on that version of code.

Regards,

Marvin