[cisco-voip] Jabber phone mode outbound calls issue

[Daniel Pagan]

Looking at the SIP transactions in a parser that doesn't display header fields (it doesn't even have the start-line) really limits how much information one can gather from the output. The REFER should have either a Replaces: header field or, most likely, a Refer-To: header field, which should give you an idea what the UAC is attempting to accomplish with that request. Seeing as how it's coming in after the UPDATE request, I would imagine the REFER might be related but I personally haven't seen that association before for a blind or consult transfer using SIP.

CCM SDL traces would help because not only would it display the SIP start-line, message header, and message body, but also SDI/SDL signals that would help explain the source of the UPDATE request and possibly the REFER if its associated. I'm assuming the 183 with SDP is for playing out the Annunciator, but again impossible to tell without the message body of the 183. Everything else before that looks normal (INVITE for the first digit, SUBSCRIBE for KPML, NOTIFY for additional digits, etc.). Detailed SDL traces from all nodes would have much more information. I personally would be more interested in the digit analysis process than anything else.

Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of abbas wali
Sent: Tuesday, November 24, 2015 12:13 PM
To: 'Ryan Huff' <ryanhuff at outlook.com>; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Jabber phone mode outbound calls issue

Hi Ryan,

Thanks for the detailed response.

Yes the issue is with Jabber clients and not the IP phones.

The line itself which is shared with many devices, can make calls on any other device but fails when made from Jabber.

I ran all the below Utils and all came out without any significant alarms
The NTP, though is at stratum 4. But again that's for both the clusters and one of them can make calls with jabber.


Have ran some traces as below
These are multiple failed calls.
Not sure why there are so many REFER messages !!

Thank s

[cid:image001.png at 01D126B9.B08386B0]

From: Ryan Huff [mailto:ryanhuff at outlook.com]
Sent: 24 November 2015 15:32
To: abbas wali <abbaseo at gmail.com<mailto:abbaseo at gmail.com>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber phone mode outbound calls issue


I assume this is only with the Jabber clients and not IP phones as well?



The annunciation message you're getting from Call Manager is typically reserved for when the calling device does not have access to the called device (or pattern). If you're confident that you're CSS/Partitions are correct you may need to look at OS level items.



I recently assisted someone who presented with similar symptoms; everything worked fine except Jabber client egress and the solution there was NTP (incorrect/unsupported NTP can cause very, very strange behavior in UCOS).



I would give the cluster a quick health check (performed from the CLI of the publisher);



  *   utils dbreplication runtimestate

     *   Looking for everything to come back with a (2) Setup Completedi message in the Replication Setup column

  *   utils diagnose module validate_network

     *   Looking for it to come back with Passed (anything fails like reverse DNS ... etc and it will explain)

  *   utils ntp status

     *   Looking for it to show synchronized and a stratum 3 (or lower)

        *   Windows servers (SNTP) are unsupported for NTP and may cause issues even if it shows synchronized

  *   utils ntp server list

     *   Looking for any ntp servers referenced by hostname/FQDN rather than IP address (you should reference ntp servers by IP address)

If everything comes back healthy, I would setup a test call scenario and pull traces off of CCM and follow the call flow. If one of the health checks fail, I would resolve that and then you may have to schedule a cluster restart (if possible).


= Ryan =





Email: ryanthomashuff at outlook.com<mailto:ryanthomashuff at outlook.com>

Spark: ryanthomashuff at outlook.com<mailto:ryanthomashuff at outlook.com>

Twitter: @ryanthomashuff<http://twitter.com/ryanthomashuff>

LinkedIn: ryanthomashuff<http://linkedin.com/in/ryanthomashuff>

Web ryanthomashuff.com<http://ryanthomashuff.com>

________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of abbas wali <abbaseo at gmail.com<mailto:abbaseo at gmail.com>>
Sent: Tuesday, November 24, 2015 9:58 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Jabber phone mode outbound calls issue


Hi all,



Jabber phone only mode (10.5.2) is unable to make any outbound calls including any internal calls even to reach the voicemail.

Inbound calls are working.



This is happening in CUCM 9.1



When dial anything , I get  the "your call cannt be completed as dialled please consult..."



I have checked via the DNA and the line settings are okay and calls permitted. Hence the CSSs\DP are okay.





Strangely, we have another cluster CM 9.1 with the same jabber version and setting and it has no issues making any calls.



Any suggestions.



Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151124/f6461c4e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 22352 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151124/f6461c4e/attachment.png>