[cisco-voip] Jabber phone mode outbound calls issue

Fri Nov 27 10:11:39 EST 2015

In your case, it seems that video capabilities might have been sent to the provider. In the case of TDM providers, this will almost always result in the call being dropped by the provider.

For TDM, You can use "voice-cap speech" on the voice port to prevent video capabilities from being sent to the provider, for SIP you could use a sip profile.

Although, an even easier method, IMO, is to adjust CCM's regional settings to prevent video capabilities from making it to the gateway (unless there are other reasons to let video capabilities to make it to the gateway such as additional sip trunks that do allow video capabilities).

-Ryan

-------- Original message --------
From: Abebe Amare
Date:11/27/2015 9:44 AM (GMT-05:00)
To: Ryan Huff
Cc: abbas wali ,cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Jabber phone mode outbound calls issue

I have encountered a similar problem in that I can't make outgoing calls to PSTN from jabber. The solution was to make the capability on the voice gateway voice port to voice only.

On Tue, Nov 24, 2015 at 10:34 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

It sounds like your solution may be changing or removing application dial rules. Application dial rules add or remove digits to dialed numbers from applications that use CCM as the call control server (e.g Unified Communications Manager IM & Presence) and do not function like traditional patterns. After an application dial rule applies its rule logic to a remote (called) number, that number must still match an egress-able pattern (or other type of onnet/offnet pattern/DN).

In practice, I do not use application dial rules for IM & Presence unless I have a specific use case; I typically allow the dialed digits from the Jabber client to enter CCM's numplan untreated by application dial rules. That said, I would not remove any of your application dial rules without first understanding why they are there and the impact it may have on other applications if they were to be removed.

The other thing to keep in mind about application dial rules is that Call Manager does not use the best match algorithm that it uses with other patterns, it applies the first dialing rule matched, which is determined by the application dial rule's priority.

You can research more on the topic on page 175 of http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmcfg/CUCM_BK_C95ABA82_00_admin-guide-100.pdf

Hope this helps,

= 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: abbas wali <abbaseo at gmail.com<mailto:abbaseo at gmail.com>>
Sent: Tuesday, November 24, 2015 2:05 PM
To: 'Ryan Huff'; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

Subject: RE: [cisco-voip] Jabber phone mode outbound calls issue

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<mailto:ryanhuff at outlook.com>]
Sent: 24 November 2015 18:30
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

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<mailto: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 01D126EA.C20EFD20]

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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151127/3bec595c/attachment.html>