05-10-2016 11:44 PM - edited 03-17-2019 06:51 AM
Peeps
Peeps,
got the following issue when calling out a trunk across to NZ.
I dial +6412345678 which is directed to another CUCM cluster in NZ, from Australia. However, as soon as it starts ringing the phone's display shows:
1012345678
which is a localized version, of the +E.164 +6412345678. This transform from +6412345678 to 1012345678 takes place in NZ and I have no control over it. I just want it to display, at all times, the +E164 number +6412345678 Below in the session progress coming from NZ across the trunk, you can see that:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.61.2.82:5060;branch=z9hG4bK28211844cd5e82
From: "Dennis Mink - 12345" <sip:+61388881234@10.2.2.2>;tag=19883330~1b5af941-cea2-4a00-a0bd-15a532224d7d-38124384
To: <sip:+6412345678@10.3.3.3>;tag=10233960~10e923c6-2538-41f6-a3ad-723d703d789a-136973409
Date: Wed, 11 May 2016 04:52:16 GMT
Call-ID: 20ed8580-7321ba80-1549a4-52023d0a@10.2.2.2
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM10.5
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Remote-Party-ID: <sip:1012345678@10.3.3.3>;party=called;screen=yes;privacy=off
P-Asserted-Identity: <sip:1012345678@10.3.3.3>
Remote-Party-ID: <sip:1012345678@10.3.3.3;user=phone>;party=x-cisco-original-called;privacy=off
Contact: <sip:+6412345678@10.3.3.3:5060;transport=tcp>
Content-Length: 0
In addition to this the call trace clearly makes a distinction between called number and remote number :
80048242.022 |14:52:17.483 |AppInfo |SIPCdpc(291395) - processRemoteIdentityInfo: num=1012345678,remoteCnNum=+6412345678;numPi=1,mCnNumPi=0;namePi=1,remoteCnNamePi=0;
I want the trunk to transform that 10XXXXX remote-perty ID and/or P-asserted ID back to the number I dialed initially, i.e. +64XXXXXXX
initially I thought this can be done through Connected Party Transform CSS on the trunk, or in the trunks device pool. But I can't seem to pull it off. Documentation on this topic is very scarce. So I am throwing it out there.
Let me know, Cheers
Solved! Go to Solution.
05-11-2016 12:07 AM
Hi Dennis,
Please check the below link if one of the way works for you.
https://supportforums.cisco.com/blog/12726551/connected-number-display-phone
- Vivek
05-11-2016 12:07 AM
Hi Dennis,
Please check the below link if one of the way works for you.
https://supportforums.cisco.com/blog/12726551/connected-number-display-phone
- Vivek
05-11-2016 09:36 PM
Vivek,
thanks for the link.
now your suggestion, to actually populate
Remote Number
on the phone, fixes the issue.
However, that would mean I would need to update all relevant phones, I was hoping I could apply it on the trunk to our remote NZ cluster, which would then need to be applied for outbound calls on the trunk. On the trunk itself I can only populate Connected Party Settings in the inbound direction, which doesn't seem right. any thoughts?
BTW the trunk is SIP cluster to cluster so, no CUBE involved that I could add sip profiles to.
05-11-2016 11:38 PM
Hi Dennis,
If you want to avoid changing it on all devices, you can use respective device pool parameter.
- Vivek
05-15-2016 06:06 PM
Yeah I now have that working on a device pool level, still wrecking my head over how to get it to work (if possible at all) on a trunk level.
Hopefully this is possible, without having to implement normalization scripts on my trunk.
05-15-2016 10:08 PM
Hi Dennis,
We have connected party transformation CSS available on SIP trunk but seems applicable only for inbound calls which doesn't seems appropriate at first sight. Let me check as soon as possible if this parameter can work for us.
- Vivek
05-15-2016 10:25 PM
Yes, correct, there seems no place to invoke it for Trunk outbound calls.
05-19-2016 07:35 PM
Vek,
did you get the chance to try that?
05-19-2016 11:26 PM
Not yet Dennis. Let me try at this weekend.
- Vivek
05-11-2016 02:16 AM
In addition to the excellent guide that Vivek (+5) has suggested, please find a similar thread on this here
https://supportforums.cisco.com/discussion/12621196/cucm-86-sip-trunk-cube-sip-trunk-ringing-connected-party-display
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