[cisco-voip] SIP gateway Caller id

Sat Jul 26 10:19:47 EDT 2014

That did the trick.

Up to about 600 ms we got pending, and once we got over that, then we got the clid name.

We used: Timers buffer-invite 1000, and worked like a champ.

Thanks,

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814
[cid:image001.png at 01CFA8AA.5CEDF8C0]<https://twitter.com/CollabSensei>
[cid:image002.png at 01CFA8AA.5CEDF8C0]<xmpp:dennis.heim at wwt.com>[cid:image003.png at 01CFA8AA.5CEDF8C0]<tel:+13142121814>[cid:image004.png at 01CFA8AA.5CEDF8C0]<sip:dennis.heim at wwt.com>

From: Daniel Pagan [mailto:dpagan at fidelus.com]
Sent: Friday, July 25, 2014 10:15 AM
To: Heim, Dennis; cisco-voip at puck.nether.net
Subject: RE: SIP gateway Caller id

I've yet to use this feature so I can't speak from experience on this specific SIP-UA timer, but it looks like using a buffered-invite timer might be helpful here. Buffered Calling-Name Completion via buffered invite:

http://www.cisco.com/c/en/us/td/docs/ios/voice/sip/configuration/guide/15_0/sip_15_0_book/sip_cg-msg_tmr_rspns.html#wp1057038

1.       Q.931 SETUP is received.

2.       SIP-UA queues the SIP INVITE request using the buffer-invite timer value

3.       Facility IE containing calling name is received

4.       SIP INVITE request is delivered with proper calling name

Hope this helps.

Daniel

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Heim, Dennis
Sent: Thursday, July 24, 2014 7:22 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] SIP gateway Caller id

PRI->2901->SIP->CUCM

We see the clid name is the Q.931 but not in any of the sip traffic to cucm. What command am I missing?

Q.931 trace:

earer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
Protocol Profile =  Networking Extensions
0xA10F02010106072A8648CE1500040A0100
Component = Invoke component
Invoke Id = 1
Operation = InformationFollowing (calling_name)
Name information in subsequent FACILITY message
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '3175551212'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '1000'
Plan:Unknown, Type:Unknown
*Jul 24 23:07:09.591: ISDN Se0/0/0:23 Q931: Received SETUP  callref = 0x81E9 callID = 0x00EF switch = primary-ni interface = User
*Jul 24 23:07:09.599: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x81E9
Channel ID i = 0xA98381
Exclusive, Channel 1
*Jul 24 23:07:09.667: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8  callref = 0x81E9
HDC-2900A#
*Jul 24 23:07:10.267: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8  callref = 0x01E9
Facility i = 0x9F8B0100A117020101020100800F574952454C4553532043414C4C4552
Protocol Profile =  Networking Extensions
0xA117020101020100800F574952454C4553532043414C4C4552
Component = Invoke component
Invoke Id = 1
Operation = CallingName
Name Presentation Allowed Extended
Name = WIRELESS CALLER
HDC-2900A#
*Jul 24 23:07:15.007: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x01E9
Cause i = 0x8090 - Normal call clearing
*Jul 24 23:07:15.007: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x81E9
*Jul 24 23:07:15.035: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x01E9
HDC-2900A#
HDC-2900A#
HDC-2900A#

SIP Messaging
HDC-2900A#
*Jul 24 23:07:37.423: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:
Sending: Binary Message Body
*Jul 24 23:07:37.423: Content-Type: application/x-q931

08 02 81 EA 05 04 03 80 90 A2 18 03 A9 83 81 1C 15 9F 8B 01 00 A1 0F 02 01 01 06 07 2A 86 48 CE 15 00 04 0A 01 00 1E 02 82 83 6C 0C 21 83 33 31 37 34 31 37 35 37 36 37 70 05 80 33 39 39 39 0D 0A
*Jul 24 23:07:37.427: //3063/235A19B380DA/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:3999@<CUCM-IP>:5060<sip:3999@%3cCUCM-IP%3e:5060> SIP/2.0

Via: SIP/2.0/UDP <GWY-IP>:5060;branch=z9hG4bK2241FD9

Remote-Party-ID: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;party=calling;screen=yes;privacy=off

From: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;tag=433E5AC-5C9

To: <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>

Date: Thu, 24 Jul 2014 23:07:37 GMT

Call-ID: 235B5203-12BE11E4-917DBA79-11ACEE9E@<GWY-IP>

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 0593107379-0314446308-2161817656-1628573152

User-Agent: Cisco-SIPGateway/IOS-15.2.4.M6a

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1406243257

Contact: <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>:5060>

Expires: 180

Allow-Events: telephone-event

Content-Type: multipart/mixed;boundary=uniqueBoundary

Mime-Version: 1.0

Content-Length: 951

--uniqueBoundary

Content-Type: application/sdp

Content-Disposition: session;handling=required

v=0

o=CiscoSystemsSIP-GW-UserAgent 3116 1746 IN IP4 <GWY-IP>

s=SIP Call

c=IN IP4 <GWY-IP>

t=0 0

m=audio 17282 RTP/AVP 0 8 18 116 101 19

c=IN IP4 <GWY-IP>

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:116 iLBC/8000

a=fmtp:116 mode=20

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtpmap:19 CN/8000

--uniqueBoundary

Content-Type: application/x-q931

Content-Disposition: signal;handling=optional

Content-Length: 65

j")
.!*HN.
.l!3175551212p3999

--uniqueBoundary

Content-Type: application/gtd

Content-Disposition: signal;handling=optional

IAM,

PRN,isdn*,,NI***,

USI,rate,c,s,c,1

USI,lay1,ulaw

TMR,00

CPN,00,,u,3999

CGN,04,,1,y,4,3175551212

CPC,09

FCI,,,,,,,y,

GCI,235a19b312be11e480dab83861120de0

--uniqueBoundary--

*Jul 24 23:07:37.431: //3063/235A19B380DA/SIP/Msg/ccsipDisplayMsg:
Received:

HDC-2900A#PuTTYPuTTYSIP/2.0 100 Trying

Via: SIP/2.0/UDP <GWY-IP>:5060;branch=z9hG4bK2241FD9

From: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;tag=433E5AC-5C9

To: <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>

Date: Thu, 24 Jul 2014 23:11:37 GMT

Call-ID: 235B5203-12BE11E4-917DBA79-11ACEE9E@<GWY-IP>

CSeq: 101 INVITE

Allow-Events: presence

Content-Length: 0

*Jul 24 23:07:37.495: //3063/235A19B380DA/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing

Via: SIP/2.0/UDP <GWY-IP>:5060;branch=z9hG4bK2241FD9

From: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;tag=433E5AC-5C9

To: <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>;tag=75717~cfc08885-a8aa-472f-9ab2-bf896a77ad81-37853857

Date: Thu, 24 Jul 2014 23:11:37 GMT

Call-ID: 235B5203-12BE11E4-917DBA79-11ACEE9E@<GWY-IP>

CSeq: 101 INVITE

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

Allow-Events: presence

Supported: X-cisco-srtp-fallback

Supported: Geolocation

P-Asserted-Identity: "Kevin Love" <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>

Remote-Party-ID: "Kevin Love" <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>;party=called;screen=yes;privacy=off

Contact: <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>:5060>;video

Content-Length: 0

*Jul 24 23:07:38.015: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:
Sending: Binary Message Body
*Jul 24 23:07:38.015: Content-Type: application/x-q931

08 02 81 EA 62 1C 1D 9F 8B 01 00 A1 17 02 01 01 02 01 00 80 0F 57 49 52 45 4C 45 53 53 20 43 41 4C 4C 45 52 0D 0A
*Jul 24 23:07:38.019: //3063/235A19B380DA/SIP/Msg/ccsipDisplayMsg:
Sent:
INFO sip:3999@<CUCM-IP>:5060<sip:3999@%3cCUCM-IP%3e:5060> SIP/2.0

Via: SIP/2.0/UDP <GWY-IP>:5060;branch=z9hG4bK2252504

From: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;tag=433E5AC-5C9

To: <sip:3999@<CUCM-IP<sip:3999@%3cCUCM-IP>>>;tag=75717~cfc08885-a8aa-472f-9ab2-bf896a77ad81-37853857

Date: Thu, 24 Jul 2014 23:07:37 GMT

Call-ID: 235B5203-12BE11E4-917DBA79-11ACEE9E@<GWY-IP>

User-Agent: Cisco-SIPGateway/IOS-15.2.4.M6a

Max-Forwards: 70

Timestamp: 1406243258

CSeq: 102 INFO

Contact: <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>:5060>

Remote-Party-ID: "3175551212" <sip:3175551212@<GWY-IP<sip:3175551212@%3cGWY-IP>>>;party=calling;screen=yes;privacy=off

Content-Type: multipart/mixed;boundary=uniqueBoundary

Mime-Version: 1.0

Content-Length: 308

--uniqueBoundary

Content-Type: application/x-q931

Content-Disposition: signal;handling=optional

Content-Length: 38

jb
.!.WIRELESS CALLER

--uniqueBoundary

Content-Type: application/gtd

Content-Disposition: signal;handling=optional

FAC,

PRN,isdn*,,NI***,

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814
[cid:image001.png at 01CFA8AA.5CEDF8C0]<https://twitter.com/CollabSensei>
[cid:image002.png at 01CFA8AA.5CEDF8C0]<xmpp:dennis.heim at wwt.com>[cid:image003.png at 01CFA8AA.5CEDF8C0]<tel:+13142121814>[cid:image004.png at 01CFA8AA.5CEDF8C0]<sip:dennis.heim at wwt.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140726/230d2776/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3876 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140726/230d2776/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1389 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140726/230d2776/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1292 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140726/230d2776/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1391 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140726/230d2776/attachment-0003.png>