CUCM Mobility/Single Number Reach is not working correctly

Bart Mars · ‎06-27-2012

Hi,

I'm experiencing difficulties with the CUCM Mobility (Single Number Reach) function.

For a customer of mine, I'm busy setting up the Mobility/Single Number Reach which is designed as follows:

- Users have a 4 digit DN that is attached to their User Device Profile so that they can use Extension Mobility.

- Those same users also have a Remote Destination Profile with a Remote Destination (to a mobile number) attached to their DN.

All has been set but as I was testing a couple of DNs, I noticed that a some numbers could be called to both their DN and Remote Destinations while others could only reach their DN.

As an example I have configured DN 6380 with the correct CSS (which permits to call to mobile phones and national numbers) to a User Device Profile.

That same DN is also connected to a Remote Destination Profile with a configured Remote Destination, which also has the same CSS.

The End User that is needed to login into Extention Mobility is 6380.

The settings on the Remote Destination are to ring always and all the time.

All Remote Destinations have the "Line Association" active.

Each DN has a value of 3 in maximum number of lines field.

Their Remote Destination profile has a value of 2 in maximum number of lines.

With this particular user, I'm sure that I have the right mobile number.

I already found out that the numbers that are having this problem, do not make a call to the PSTN and mobile network when their DN are called.

So I think the problem is within CUCM.

Can somebody help me?

Many thanks in advance!

The version of call manager is 8.6.2.20000-2.

Chris Deren · ‎06-27-2012

Does the call make it to the GW?

Have you looked at SDI traces?

Sent from Cisco Technical Support iPhone App

Bart Mars · ‎06-27-2012

Hi Chris,

All I can say is that the calls are not going to the PSTN and the mobile network.

I'm not familiar with (SDI) traces, so I hope to provide you some good information:

14:02:41.601 |insertIntoCiCdccMapList(42512882) (2,100,207,169622)|*^*^*

14:02:41.601 |SdiStats: #Lines: 9 Free HWM: 9 Free HWM(total): 67|*^*^*

14:02:41.601 |insertIntoCiCdccMapList(42512890) (2,100,207,169622)|*^*^*

14:02:41.605 |removeFromCiCdccMap(42512890)|*^*^*

14:02:41.605 |removeFromCiCdccMap(42512882)|*^*^*

14:02:41.605 |removeFromCiCdccMap(0)|*^*^*

14:04:23.691 |insertIntoCiCdccMapList(42512897) (2,100,207,169630)|*^*^*

14:04:23.691 |SdiStats: #Lines: 9 Free HWM: 6 Free HWM(total): 67|*^*^*

14:04:23.691 |insertIntoCiCdccMapList(42512928) (2,100,207,169630)|*^*^*

14:04:23.696 |removeFromCiCdccMap(42512928)|*^*^*

14:04:23.696 |removeFromCiCdccMap(42512897)|*^*^*

14:04:23.696 |removeFromCiCdccMap(0)|*^*^*

14:05:41.934 |insertIntoCiCdccMapList(42512933) (2,100,207,169645)|*^*^*

14:05:41.934 |SdiStats: #Lines: 9 Free HWM: 6 Free HWM(total): 67|*^*^*

14:05:41.934 |insertIntoCiCdccMapList(42512943) (2,100,207,169645)|*^*^*

14:05:41.941 |removeFromCiCdccMap(42512943)|*^*^*

14:05:41.941 |removeFromCiCdccMap(42512933)|*^*^*

14:05:41.941 |removeFromCiCdccMap(0)|*^*^*

What will a SDI trace do?

ah2760001 · ‎12-30-2013

i have incountered similar problem. the call apreares on the getway but not calling on the mobile phone

Chris Deren · ‎06-27-2012

Do a debug on the GW, ie " debug isdn Q931" with PRI circuit.

SDI are CUCM traces that would reveal relavent routing and issues.

Sent from Cisco Technical Support iPhone App

Bart Mars · ‎06-28-2012

I did a debug isdn q931 on the voice router which is connected to the PRI circuit.

A couple of test calls later and this is the output I got:

Jun 28 08:34:15.737: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0E5A

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18382

Preferred, Channel 2

Calling Party Number i = 0x2183, '51365XXXX'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '88777XXXX'

Plan:ISDN, Type:National

Sending Complete

Jun 28 08:34:15.749: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8E5A

Channel ID i = 0xA98382

Exclusive, Channel 2

This company has 200+ Mobility users so I did a random check.

Strangely enough, the one I described in my first post is now reachable on both his DN and mobile phone.

This is 4 digit number was the only one though.

Jun 28 08:09:20.557: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x00A6

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18382

Preferred, Channel 2

Calling Party Number i = 0x2181, '51365XXXX'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '88777XXXX'

Plan:ISDN, Type:National

High Layer Compat i = 0x9181

Sending Complete

Jun 28 08:09:20.569: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x80A6

Channel ID i = 0xA98382

Exclusive, Channel 2

Jun 28 08:09:20.573: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x2345

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839C

Exclusive, Channel 28

Display i = 'Testnummer'

Called Party Number i = 0x80, '51365XXXX'

Plan:Unknown, Type:Unknown

Redirecting Number i = 0x00008F, '088777XXXX'

Plan:Unknown, Type:Unknown

I did a Remote Destination Profile export of all records with a Remote Destination attached to it and then re-imported them in CUCM.

The last output of the call to the mobile phone was not appearing last Thursday.

Apparently, the export and import of the profiles and destinations did change something within CUCM.

Could this be a bug in CUCM?