Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CUCM - P-Asserted-Identity

Topology: CUCM ---- SIP ---- CUBE ---- SIP ---- SP

Sometimes, when I place a call, it redirects it to an internal extension. The only SIP message that I can see being sent when that happens is a 180 ringing with a p-asserted-identity in it. It only happens about 50% of the time. example: I dial 9.8001234567 and end up talking to someone at extension 3041. The Dialed Number Analyzer shows everything correctly. This SIP message is below. HELP!! please

10/01/2013 08:59:39.274 CCM|//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to  -CUBE--->10.3.20.240:[5060]:

SIP/2.0 180 Ringing

Date: Tue, 01 Oct 2013 13:59:39 GMT

Call-Info: <sip:-CUCM--->10.3.20.10:5060>;method="NOTIFY;Event=telephone-event;Duration=500"

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

From: <sip:5141234567@--SP Edge device----->22.22.22.22>;tag=739821B4-19C2

Allow-Events: presence

P-Asserted-Identity: "Switchboard" <sip:3041@10.3.20.10>

Supported: X-cisco-srtp-fallback

Supported: Geolocation

Remote-Party-ID: "Switchboard" <sip:3041@10.3.20.10>;party=called;screen=yes;privacy=off

Content-Length: 0

To: <sip:8001234567@10.3.20.10>;tag=87d22a15-fd7d-492e-85ed-0dc8d67386d5-30912190

Contact: <sip:8001234567@10.3.20.10:5060>

Call-ID: 8728F540-29D811E3-95F9916C-119656@10.3.20.240

Via: SIP/2.0/UDP 10.3.20.240:5060;branch=z9hG4bK2D01637

CSeq: 101 INVITE

1 REPLY
VIP Super Bronze

CUCM - P-Asserted-Identity

My guess is that the call got hairpinned back to CUCM by the provider or CUBE. We need to see the full trace from CUBE to be sure. PAI is really just attempting to indicate who the call is actually alerting because the From and To headers cannot change after the INVITE message.

The fact that CUCM is sending a 180 RINGING message implies that it is processing an *incoming* call. This is reinforced by the headers because the From header is the SP SBC, the via header is CUBE, and the To header is CUCM. Inbound call!

Compare the Call-ID of the SIP INVITE CUCM first sends to CUBE for your outbound call to the one shown in this message. Are they different?

Run these if you want us to look deeper. If you have multiple calls going be certain to point out the calling/called number and the IPs if any differ from what you have called out above.

show run | section dial-peer

debug ccsip messages

debug voip dialpeer

Please remember to rate helpful responses and identify helpful or correct answers.

1183
Views
0
Helpful
1
Replies
CreatePlease to create content