+E.164 format call not working

[srivatsan04]

Hi,

I have two CIPC (HQ1 and HQ2) registered with CUCM 11.5 with directory number +12012012001, +12012012002 respectively. Also, I configured Enterprise Alternate number (6-digit format) for both the phones.

1. When I try to call hq1 from hq2 the call works with both 6-digit and +E.164 format.

2. When I try to call hq2 from hq1 the call does not reaches with +E.164 format but, the call reaches hq2 with 6-digit format.

3. One more thing is that when I call +12012012001 (hq1 phone directory number) from hq1 the call is unsuccessful. But, 6-digit format call from hq1 to hq1 works.

From this I found that hq1 can not call +E.164 format calls.

Note: Both the Phones are configured with same partition and css. Both the phones CIPC version are also same. Only difference between them is hq1 is a SIP device and hq2 is a SCCP device.

Can anyone help me with this issue?

[Georgios Fotiadis]

Which version of CIPC are you using?

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCsv63788/?referring_site=bugquickviewredir

[srivatsan04]

CIPC version is 8.6.5

[Georgios Fotiadis]

Hm, that should be working. Can you collect and attach "Cisco CallManager" SDL logs?

[Joe Vallender]

You might also have a CUCM administrator do a Dialed Number Analyzer  test to see how all the related dialing strings are handled.

[srivatsan04]

Sry for the late reply Georgios, take a look at the SDL logs you asked and reply me if you found anything.

00065878.003 |17:17:38.375 |AppInfo |SMDMSharedData::findLocalDevice - Name=+12012012002:449f4654-1ebf-10ab-4a32-e94798e71d0e Key=6753dcc3-a0e3-4961-10d7-c6f307ea2a8a isActvie=1 Pid=(2,176,32) found
00065879.000 |17:17:38.375 |SdlSig |DmPidRes |wait |Da(2,100,214,1) |DeviceManager(2,100,208,1) |2,100,14,52.58^10.1.110.201^SEP000000002001 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] Cepn=6753dcc3-a0e3-4961-10d7-c6f307ea2a8a Id=3857512720 ccmType=4 DeviceName=+12012012002:449f4654-1ebf-10ab-4a32-e94798e71d0e Pid=2,100,176,32,ad243d17-98b4-4118-8feb-5ff2e1b781ac
00065879.001 |17:17:38.375 |AppInfo |Digit analysis: wait_DmPidRes- Partition=[449f4654-1ebf-10ab-4a32-e94798e71d0e] Pattern=[812002] Where=[],cmDeviceType=[UserDevice], OutsideDialtone =[0], DeviceOverride=[0], PID=LineControl(2,100,176,32),CI=[46115512],Sender=Cdcc(2,100,222,25)
00065880.000 |17:17:38.375 |SdlSig |DaRes |setup_da |Cdcc(2,100,222,25) |Da(2,100,214,1) |2,100,14,52.58^10.1.110.201^SEP000000002001 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=46115512 Dial NoPotentialMatchesExist OnNet PretransformCgpn=tn=0npi=0ti=3nd=+12012012001User=hq1Host=hq.cisco.comPort=0PassWord=Madder=Transport=4mDisplayName=RawUrl=OrigPort=0pi=0si1 Cgpn=tn=0npi=0ti=3nd=+12012012001User=hq1Host=hq.cisco.comPort=0PassWord=Madder=Transport=4mDisplayName=RawUrl=OrigPort=0pi=0si1 DialingPartition=449f4654-1ebf-10ab-4a32-e94798e71d0e DialingPattern=812002 DialingRPRE=(812002) PID=(2,176,32) PretransformCdpn=tn=0npi=0ti=3nd=812002User=hq2Host=hq.cisco.comPort=0PassWord=Madder=Transport=4mDisplayName=RawUrl=OrigPort=0pi=0si0 PretransformTags=SUBSCRIBER PretransformPos=812002

[R0g22]

Can you attach the complete SDL folder ? This just has the device manager PID response (DmPidRes).

[srivatsan04]

Hi Nipun Singh, 

I have attached the full SDL trace file as you requested. Please feel free to use it and find the solution.

[srivatsan04]

In addition i found that E.164 call is working in CIPC SCCP device, but not in CIPC SIP device. Also I used SIP X-Lite (Third Party application) to test whether SIP device can work with E.164 format call and it worked. So, there seems to be no problem in SIP devices. Only when i use CIPC with SIP protocol I get this issue.

Another method i tried is using new CUCM and both SIP as well as SCCP CIPC E.164 calls were working in it. I get the issue in old CUCM.

[Georgios Fotiadis]

What exactly happens when you dial the E.164 number (2001)?

I see this on the logs:

00061570.006 |17:05:26.708 |AppInfo  |Digit analysis: match(pi="2", fqcn="+12012012002", cn="+12012012002",plv="5", pss="HQ-DN:BR2-DN:HQ", TodFilteredPss="HQ-DN:BR2-DN:HQ", dd="+12012012001",dac="0")
...INVITE...
...RINGING...
00061655.001 |17:05:28.980 |AppInfo  |StationInit: (0000004) SoftKeyEvent softKeyEvent=9(EndCall) lineInstance=1 callReference=46115493.

which suggests that CUCM received and Endcall event.

Can you perform again a successful 6-digit call and an unsuccessful E.164 and re-attach logs.

[srivatsan04]

Hi Georgios,

As you requested, i made successful 6-digit call and an unsuccessful E.164 and attached the SDL trace log.

[Georgios Fotiadis]

What is the alternate 6-digit number your are dialing? There is no such call in the previously attached logs. Can you attach logs with such a call?

[srivatsan04]

Hi Georgios,

The 6-digit number is 812001 for hq1 and 812002 for hq2. I already attached successful 6-digit dialing but since you requested i have made 6-digit call from hq1 to hq2(812002) and E.164 dialing also in the attachment i reply now.

[Georgios Fotiadis]

Thank you, now the second call is present in the logs. Looks like the call is disconnected at some point after CUCM receives the 180 Ringing messages from the IP phone, when it is dialed as E.164. I would attribute this to firmware bug of CIPC; maybe TAC (or someone else in here) can give you more info about it, but nothing weird is shown in the logs that points to mis-configuration. Unfortunately CIPC is End-of-Support, so no new firmware versions...

Suggestions:

- Use Cisco Jabber instead of CIPC

- Use a translation pattern to transform E.164 to 4-digit so to avoid E.164 numbers directly on the phones.

[srivatsan04]

Actually as i said before its not CIPC issue because with new CUCM I configured SIP and SCCP CIPC device with E.164 format DN and the calls are working either way. But I need to solve the issue in old CUCM and it has issue in E.164 format call issue for SIP CIPC.