[cisco-voip] Jabber phone mode outbound calls issue

abbas wali abbaseo at gmail.com
Tue Nov 24 14:05:01 EST 2015


Its set to Standard Analysis. 

 

Something else I have noticed. 

There are application dial rules defined. On top (with top priority ) there
was Default rule beginning with blank, 0 digit strip and append 8. 

 

Some of the traces I found all my dials were appended by 8.

 

Okay I have now moved the default dial rule to the bottom and all the
correct one are on top. 

 

Now I can dial internally across cluster which is good. But cant dial
external 

 

If that's the case and have to define full dial plan in the app dial rule
that will become quiet messy. 

 

 

 

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

 

Also and if it isn't too late, before you pull the SDL trace on the test
call, can you verify that the Digit Complexity Analysis is set to
TranslationAndAlternatePatternAnalysis under Service Parameters->Cisco Call
Manager?

 

= 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 Ryan Huff
<ryanhuff at outlook.com <mailto:ryanhuff at outlook.com> >
Sent: Tuesday, November 24, 2015 1:00 PM
To: abbas wali; cisco-voip at puck.nether.net
<mailto:cisco-voip at puck.nether.net> 
Subject: Re: [cisco-voip] Jabber phone mode outbound calls issue 

 

I would deffinatley look into getting the clock sync to a strata 3 on the
pub and then restart ntp services.

 

Can you do a test call on one of the Jabber clients and pull of the SDL
traces for the call?

 

 

Sent from my T-Mobile 4G LTE Device



-------- Original message --------
From: abbas wali 
Date:11/24/2015 12:13 PM (GMT-05:00) 
To: 'Ryan Huff' ,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

 



 

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 < <mailto:cisco-voip-bounces at puck.nether.net>
cisco-voip-bounces at puck.nether.net> on behalf of abbas wali <
<mailto:abbaseo at gmail.com> abbaseo at gmail.com>
Sent: Tuesday, November 24, 2015 9:58 AM
To:  <mailto:cisco-voip at puck.nether.net> 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/b84d805a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 22352 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151124/b84d805a/attachment.png>


More information about the cisco-voip mailing list