12-03-2017 08:23 PM - edited 03-13-2019 10:06 PM
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?
Solved! Go to Solution.
02-27-2018 03:08 AM
The issue is in my route pattern where i unchecked Urgent priority checkbox and the issue is solved.
12-06-2017 01:57 AM
Which version of CIPC are you using?
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCsv63788/?referring_site=bugquickviewredir
12-06-2017 04:25 AM
CIPC version is 8.6.5
12-06-2017 09:55 AM
Hm, that should be working. Can you collect and attach "Cisco CallManager" SDL logs?
12-07-2017 09:00 AM
You might also have a CUCM administrator do a Dialed Number Analyzer test to see how all the related dialing strings are handled.
01-30-2018 01:30 AM
01-30-2018 10:46 AM
01-30-2018 07:10 PM
01-30-2018 07:18 PM
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.
01-31-2018 04:21 AM
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.
01-31-2018 05:04 AM
02-01-2018 03:57 AM - edited 02-01-2018 04:01 AM
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?
02-01-2018 04:36 AM
02-01-2018 04:58 AM
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.
02-01-2018 07:32 PM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide