Twinning Caller ID SIP Trunk, Server Edition 10.1

[acollard83]

I am having an issue with right now just 1 user and the caller ID on mobile twinning. For all other users, IP Office passes the caller id, but for one specific user, it uses his extension number. SIP Invites are below. This is Server Edition Select, 10.1 with an IP500v2 as a media gateway for digital phones and a couple analog phones (fax machine and old conference phones). Not sure why it is different with the 2 extensions. The only thing that is different is that the extension with the issue is currently not logged in to a phone, which could have something to do with it.

Good Call, passed caller id number through to cell phone
12:22:18 839737069mS SIP Tx: UDP 10.22.100.10:5060 -> X.X.X.X:5060
INVITE sip:1517441XXX@X.X.X.X SIP/2.0
Via: SIP/2.0/UDP 10.22.100.10:5060;rport;branch=z9hG4bK06a715f7615ff877eba2c66ec597eff0
From: "GRAND RAPIDS MI" <sip:616226XXX@X.X.X.X>;tag=8b34bcc81b83c527
To: <sip:1517441XXXX@X.X.X.X>
Call-ID: 40a96f027c28d6afd4954a9d27dee2e0
CSeq: 1221410888 INVITE
Contact: "GRAND RAPIDS MI" <sip:616226XXXX@10.22.100.10:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 10.1.0.0.0 build 237
P-Asserted-Identity: "GRAND RAPIDS MI" <sip:616226XXXX@X.X.X.X:5060>
Content-Type: application/sdp
Content-Length: 204

v=0
o=UserA 1554149772 1540220624 IN IP4 10.22.100.10
s=Session SDP
c=IN IP4 10.22.100.10
t=0 0
m=audio 42736 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Bad call, didn't pass caller id
12:24:37 839875680mS SIP Tx: UDP 10.22.100.10:5060 -> X.X.X.X:5060
INVITE sip:1517667XXXX@X.X.X.X SIP/2.0
Via: SIP/2.0/UDP 10.22.100.10:5060;rport;branch=z9hG4bK67236d28b5286394b169513a2089e2d4
From: "GRAND RAPIDS MI" <sip:616226XXXX@X.X.X.X>;tag=295b6812fc2e384a
To: <sip:1517667XXXX@X.X.X.X>
Call-ID: 60ed85c6a128692275045ca9a71eb0dc
CSeq: 1237032618 INVITE
Contact: "Wayne" <sip:8299@10.22.100.10:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 10.1.0.0.0 build 237
P-Asserted-Identity: "Wayne" <sip:8299@X.X>X.X:5060>
Content-Type: application/sdp
Content-Length: 203

v=0
o=UserA 384287271 1289355654 IN IP4 10.22.100.10
s=Session SDP
c=IN IP4 10.22.100.10
t=0 0
m=audio 42740 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

 

[NYSTECH]

Do you have User | SIP | Anonymous checked or unchecked.

 

[acollard83]

Unchecked on both.

 

[Pepp77]

Both the contact and the PAI are different, are they using different URI's due to a user shortcode?

| ACSS SME |

 

[acollard83]

No user shortcodes.

I am wondering if it is because the user is not logged in to a phone. He is currently the only twinned user that isn't, and also the only one with this issue. I am going to test this theory today.

 

[janni78]

The user don't need to have a phone, out systems usually have 95% phoneless users.

Most likely this is a configuration issue.

"Trying is the first step to failure..." - Homer

 

[acollard83]

I'm looking, but there is nothing different in the users config. It is only this one user that the caller ID doesn't pass through when twinning.

 

[janni78]

You need to look at the full trace of both calls, with the limited information available I just as well spend my luck on a lotto ticket =)

"Trying is the first step to failure..." - Homer

 

[acollard83]

I've attached the call trace from Monitor for the call that doesn't pass through the caller id. The good call will follow.

 

[janni78]

What SIP URIs do you have on your SIP trunk?

"Trying is the first step to failure..." - Homer

 

[acollard83]

And here is the call that passes caller id correctly

 

[janni78]

Is the SIP tab correct on the user not working?

"Trying is the first step to failure..." - Homer

 

[derfloh]

Seems like 10.1.0 has an issue with PAI. I have two systems where PAI is set correct for Call forwarding but it is totally missing for twinned calls.

 

[janni78]

It works on my 10.1, might depend what you're using it for.

"Trying is the first step to failure..." - Homer

 

[derfloh]

To present the correct number for mobile twinning. Provider expects a number belonging to the trunk as PAI to allow sending foreign caller ID.

Works well on 10.0 SP3. On 10.1 it only works for call forwarding but not for twinning.

 

[acollard83]

So it looks as if I figured it out. We will continue to test though.

I had PAI set as Send Caller ID in the Forwarding and Twinning section of the trunk. I changed it to RPID and it worked. Still curious as to why it passed the caller id when twinned on other extension when it was set to PAI.

Thanks again for all the help.

 

[Pepp77]

I always use Diversion header for forwarded CLI and haven't had an issue yet.

| ACSS SME |

 

[janni78]

I always use Diversion header for forwarded CLI and haven't had an issue yet.

Most providers here support DH as well, but some will only look at PAI.

"Trying is the first step to failure..." - Homer