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

Problems with CUE AA to CME extension.

Hello,

     I am running into an issue with my CME/CUE configuration where whenever a caller tries dialing an extension during the AA announcement (or from the dial by extension menu option), they get a message (I'm guessing from CUE) that the subscriber they are trying to reach is not available, and the system drops the call.  Whenever you dial the AA DN from an internal extension, using the AA to dial an extension works fine.

     This was working fine since I setup the system, but in the last few days has stopped working.  After taking a look at the ccsip messages, it appears that CUE is transferring to CME with a called-id of the main DID instead of the extension selected by the caller.  Our PSTN link is some SIP trunks (Nextiva).  Any ideas on where to go with this next will be greatly appreciated.

===================================================================================

ccsip messages for a call coming off of the Nextiva SIP trunks through CUE, and dialing an extension (1103).

hlsm-2821#

Jul 24 19:26:40.823: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

REGISTER sip:trunking.voipdnsservers.com:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.10.12:5060;branch=z9hG4bK8A4BC5

From: <sip:xxxxxxxxx@trunking.voipdnsservers.com>;tag=4987AC8-25EE

To: <sip:xxxxxxxxx@trunking.voipdnsservers.com>

Date: Wed, 24 Jul 2013 19:26:40 GMT

Call-ID: 5AD392DA-F31E11E2-8002FDEF-396CC98A

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1374694000

CSeq: 1326 REGISTER

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>

Expires:  3600

Supported: path

Content-Length: 0

Jul 24 19:26:40.927: //2396/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.1.10.12:5060;received=23.31.253.222;branch=z9hG4bK8A4BC5;rport=63328

From: <sip:xxxxxxxxx@trunking.voipdnsservers.com>;tag=4987AC8-25EE

To: <sip:xxxxxxxxx@trunking.voipdnsservers.com>;tag=aprqhje8503-j2bd9k10081s2

Call-ID: 5AD392DA-F31E11E2-8002FDEF-396CC98A

Timestamp: 1374694000

CSeq: 1326 REGISTER

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>;expires=46

Jul 24 19:26:44.207: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKi25tco10e800vntfg0i0.1

Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay,  multipart/mixed

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Disposition: session; handling=required

Content-Length: 238

Content-Type: application/sdp

CSeq: 1 INVITE

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

In-Reply-To: 436809728_8630707@207.155.147.62

Session-Expires: 1800;refresher=uas

Supported: timer

To: <sip:5702665351@192.168.101.100>

Max-Forwards: 70

v=0

o=Sonus_UAC 32325 22772 IN IP4 208.73.146.xx

s=SIP Media Capabilities

c=IN IP4 208.73.146.xx

t=0 0

m=audio 32234 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

a=maxptime:20

Jul 24 19:26:44.219: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKi25tco10e800vntfg0i0.1

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 1 INVITE

Allow-Events: telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

Jul 24 19:26:44.231: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A556C

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

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

Min-SE:  1800

Cisco-Guid: 3473690596-4090302946-2322398703-0963430794

User-Agent: Cisco-SIPGateway/IOS-12.x

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

CSeq: 101 INVITE

Timestamp: 1374694004

Contact: <sip:xxxxxxxxxx@172.20.100.10:5060>

Call-Info: <sip:172.20.100.10:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 69

Session-Expires:  1800;refresher=uas

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 193

v=0

o=CiscoSystemsSIP-GW-UserAgent 9413 868 IN IP4 172.20.100.10

s=SIP Call

c=IN IP4 172.20.100.10

t=0 0

m=audio 17280 RTP/AVP 0

c=IN IP4 172.20.100.10

a=rtpmap:0 PCMU/8000

a=ptime:20

Jul 24 19:26:44.259: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A556C

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 0

Timestamp: 1374694004

Contact: <sip:1191@172.20.100.20:5060>

Jul 24 19:26:44.303: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A556C

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 0

Contact: <sip:1191@172.20.100.20:5060>

Jul 24 19:26:44.307: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKi25tco10e800vntfg0i0.1

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 1 INVITE

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

Allow-Events: telephone-event

Contact: <sip:1191@10.1.10.12:5060>

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

Jul 24 19:26:44.431: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A556C

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 180

Contact: <sip:1191@172.20.100.20:5060>

Content-Type: application/sdp

Call-Info: <sip:172.20.100.20:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"

Allow-Events: telephone-event

v=0

o=CiscoSystemsSIP-Workflow-App-UserAgent 1740 1740 IN IP4 172.20.100.20

s=SIP Call

c=IN IP4 172.20.100.20

t=0 0

m=audio 16908 RTP/AVP 0

a=rtpmap:0 pcmu/8000

a=ptime:20

Jul 24 19:26:44.439: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A647C

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Jul 24 19:26:44.447: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKi25tco10e800vntfg0i0.1

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 1 INVITE

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

Allow-Events: telephone-event

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>

Supported: replaces

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Supported: timer

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 241

v=0

o=CiscoSystemsSIP-GW-UserAgent 4827 3500 IN IP4 10.1.10.12

s=SIP Call

c=IN IP4 10.1.10.12

t=0 0

m=audio 19008 RTP/AVP 0 101

c=IN IP4 10.1.10.12

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

Jul 24 19:26:44.547: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKi25tco10e800vntfg0i0.1

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Date: Wed, 24 Jul 2013 19:26:44 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 1 INVITE

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

Allow-Events: telephone-event

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>

Supported: replaces

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Supported: timer

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 241

v=0

o=CiscoSystemsSIP-GW-UserAgent 4827 3500 IN IP4 10.1.10.12

s=SIP Call

c=IN IP4 10.1.10.12

t=0 0

m=audio 19008 RTP/AVP 0 101

c=IN IP4 10.1.10.12

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

Jul 24 19:26:44.599: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Content-Length: 0

CSeq: 1 ACK

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

Jul 24 19:26:44.643: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Content-Length: 0

CSeq: 1 ACK

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

Jul 24 19:26:49.103: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:49.103: Content-Type: audio/telephone-event

01 00 07 D0

Jul 24 19:26:49.107: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A7C1F

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 102 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:49 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:26:49.119: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A7C1F

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 102 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:49.183: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:49.183: Content-Type: audio/telephone-event

01 80 00 50

Jul 24 19:26:49.187: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A81C08

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 103 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:49 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:26:49.199: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A81C08

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 103 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:50.023: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:50.023: Content-Type: audio/telephone-event

01 00 07 D0

Jul 24 19:26:50.027: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A913D3

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 104 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:50 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:26:50.039: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8A913D3

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 104 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:50.103: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:50.103: Content-Type: audio/telephone-event

01 80 00 50

Jul 24 19:26:50.107: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AAA03

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 105 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:50 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:26:50.119: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AAA03

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 105 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:50.623: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:50.623: Content-Type: audio/telephone-event

00 00 07 D0

Jul 24 19:26:50.627: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8ABB06

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 106 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:50 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

..P

Jul 24 19:26:50.639: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8ABB06

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 106 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:50.703: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:50.703: Content-Type: audio/telephone-event

00 80 00 50

Jul 24 19:26:50.707: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AC2068

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 107 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:50 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

..P

Jul 24 19:26:50.719: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AC2068

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 107 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:51.223: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:51.223: Content-Type: audio/telephone-event

03 00 07 D0

Jul 24 19:26:51.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AD1E73

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 108 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:51 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:26:51.239: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AD1E73

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 108 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:51.303: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:26:51.303: Content-Type: audio/telephone-event

03 80 00 4B

Jul 24 19:26:51.307: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AECE6

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 109 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:26:51 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.K

Jul 24 19:26:51.319: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8AECE6

To: <sip:1191@172.20.100.20>;tag=cue26a9e987

From: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 109 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:26:57.343: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:xxxxxxxxxx@172.20.100.10:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~166

Max-Forwards: 70

To: <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

From: <sip:1191@172.20.100.20>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 1 BYE

Content-Length: 0

Contact: <sip:1191@172.20.100.20:5060>

Also: <sip:1103@172.20.100.10:5060;user=phone>

Jul 24 19:26:57.343: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~166

From: <sip:1191@172.20.100.20>;tag=cue26a9e987

To: "WIRELESS CALLER" <sip:xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Date: Wed, 24 Jul 2013 19:26:57 GMT

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 BYE

P-RTP-Stat: PS=681,OS=102096,PR=430,OR=68323,PL=0,JI=0,LA=0,DU=12

Content-Length: 0

Jul 24 19:26:57.351: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.10.12:5060;branch=z9hG4bK8AF1BEB

From: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

To: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Date: Wed, 24 Jul 2013 19:26:57 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

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

Min-SE:  1800

Cisco-Guid: 3473690596-4090302946-2322398703-0963430794

User-Agent: Cisco-SIPGateway/IOS-12.x

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

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1374694017

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 253

v=0

o=CiscoSystemsSIP-GW-UserAgent 4827 3501 IN IP4 10.1.10.12

s=SIP Call

c=IN IP4 10.1.10.12

t=0 0

m=audio 19008 RTP/AVP 0 101

c=IN IP4 10.1.10.12

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendonly

Jul 24 19:26:57.579: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.1.10.12:5060;received=23.31.253.222;branch=z9hG4bK8AF1BEB;rport=63328

From: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

To: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 101 INVITE

Timestamp: 1374694017

Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay,  multipart/mixed

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 238

Content-Type: application/sdp

v=0

o=Sonus_UAC 32325 22773 IN IP4 208.73.146.xx

s=SIP Media Capabilities

c=IN IP4 208.73.146.xx

t=0 0

m=audio 32234 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=recvonly

a=maxptime:20

Jul 24 19:26:57.587: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.10.12:5060;branch=z9hG4bK8B020A0

From: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

To: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Date: Wed, 24 Jul 2013 19:26:57 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Jul 24 19:26:57.587: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

REFER sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.10.12:5060;branch=z9hG4bK8B1AB9

From: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

To: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 102 REFER

Max-Forwards: 70

Contact: <sip:xxxxxxxxx@10.1.10.12:5060>

User-Agent: Cisco-SIPGateway/IOS-12.x

Timestamp: 1374694017

Refer-To: sip:1103@10.1.10.12

Referred-By: <sip:xxxxxxxxx@trunking.voipdnsservers.com>

Content-Length: 0

Jul 24 19:26:57.727: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP 10.1.10.12:5060;received=23.31.253.222;branch=z9hG4bK8B1AB9;rport=63328

From: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

To: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Call-ID: pcst13746940041508191241310@192.168.201.118

CSeq: 102 REFER

Timestamp: 1374694017

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 0

Jul 24 19:26:57.731: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000g10.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 20

Content-Type: message/sipfrag

CSeq: 3 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: active;expires=3600

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 100 Trying

Jul 24 19:26:58.071: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000020.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 22

Content-Type: message/sipfrag

CSeq: 4 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: terminated;reason=noresource

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 404 Not Found

Jul 24 19:26:58.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000g10.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 20

Content-Type: message/sipfrag

CSeq: 3 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: active;expires=3600

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 100 Trying

Jul 24 19:26:58.571: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000020.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 22

Content-Type: message/sipfrag

CSeq: 4 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: terminated;reason=noresource

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 404 Not Found

Jul 24 19:26:59.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000g10.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 20

Content-Type: message/sipfrag

CSeq: 3 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: active;expires=3600

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 100 Trying

Jul 24 19:26:59.571: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000020.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 22

Content-Type: message/sipfrag

CSeq: 4 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: terminated;reason=noresource

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 404 Not Found

Jul 24 19:27:01.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000g10.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 20

Content-Type: message/sipfrag

CSeq: 3 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: active;expires=3600

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 100 Trying

Jul 24 19:27:01.571: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370ck0000020.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Contact: <sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp>

Content-Length: 22

Content-Type: message/sipfrag

CSeq: 4 NOTIFY

Event: refer

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

Subscription-State: terminated;reason=noresource

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

SIP/2.0 404 Not Found

Jul 24 19:27:01.775: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:xxxxxxxxx@10.1.10.12:5060 SIP/2.0

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370cd0000030.1

Call-Id: pcst13746940041508191241310@192.168.201.118

Content-Length: 0

CSeq: 6 BYE

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Max-Forwards: 70

Jul 24 19:27:01.783: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

no deSIP/2.0 200 OK

Via: SIP/2.0/UDP 208.73.146.xx:5060;branch=z9hG4bKjr5gsu004gg1cqpml370cd0000030.1

From: "WIRELESS CALLER"  <sip:xxxxxxxxxx@192.168.101.118:5060;otg=TG_CORE_GSX;pstn-params=808482808882>;tag=gK0911fe0e

To: <sip:5702665351@192.168.101.100>;tag=4988864-3B7

Date: Wed, 24 Jul 2013 19:27:01 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 6 BYE

Reason: Q.850;cause=16

P-RTP-Stat: PS=430,OS=68323,PR=682,OR=102256,PL=0,JI=0,LA=0,DU=17

Content-Length: 0

=========================================================================================

ccsip messages for a call to the AA from an internal extension, and dialing by extension from there.

Jul 24 19:31:55.492: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8D83CD

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>

Date: Wed, 24 Jul 2013 19:31:55 GMT

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

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

Min-SE:  1800

Cisco-Guid: 2277454902-4090368482-2324102639-0963430794

User-Agent: Cisco-SIPGateway/IOS-12.x

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

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1374694315

Contact: <sip:1103@172.20.100.10:5060>

Call-Info: <sip:172.20.100.10:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 194

v=0

o=CiscoSystemsSIP-GW-UserAgent 8960 6838 IN IP4 172.20.100.10

s=SIP Call

c=IN IP4 172.20.100.10

t=0 0

m=audio 17210 RTP/AVP 0

c=IN IP4 172.20.100.10

a=rtpmap:0 PCMU/8000

a=ptime:20

Jul 24 19:31:55.512: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8D83CD

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 0

Timestamp: 1374694315

Contact: <sip:1191@172.20.100.20:5060>

Jul 24 19:31:55.552: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8D83CD

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 0

Contact: <sip:1191@172.20.100.20:5060>

Jul 24 19:31:55.628: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8D83CD

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 101 INVITE

Content-Length: 180

Contact: <sip:1191@172.20.100.20:5060>

Content-Type: application/sdp

Call-Info: <sip:172.20.100.20:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"

Allow-Events: telephone-event

v=0

o=CiscoSystemsSIP-Workflow-App-UserAgent 1638 1638 IN IP4 172.20.100.20

s=SIP Call

c=IN IP4 172.20.100.20

t=0 0

m=audio 16900 RTP/AVP 0

a=rtpmap:0 pcmu/8000

a=ptime:20

Jul 24 19:31:55.644: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8D9143E

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Date: Wed, 24 Jul 2013 19:31:55 GMT

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Jul 24 19:31:57.748: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:57.748: Content-Type: audio/telephone-event

01 00 07 D0

Jul 24 19:31:57.748: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DA103E

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 102 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:57 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:31:57.760: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DA103E

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 102 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:57.764: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:57.764: Content-Type: audio/telephone-event

01 80 00 64

Jul 24 19:31:57.764: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DB14A9

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 103 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:57 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.d

Jul 24 19:31:57.780: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DB14A9

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 103 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:57.896: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:57.896: Content-Type: audio/telephone-event

01 00 07 D0

Jul 24 19:31:57.896: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DC78F

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 104 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:57 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:31:57.912: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DC78F

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 104 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:57.912: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:57.912: Content-Type: audio/telephone-event

01 80 00 64

Jul 24 19:31:57.912: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DD300

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 105 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:57 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.d

Jul 24 19:31:57.928: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DD300

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 105 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:58.288: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:58.288: Content-Type: audio/telephone-event

00 00 07 D0

Jul 24 19:31:58.288: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DE10B0

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 106 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:58 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

..P

Jul 24 19:31:58.300: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DE10B0

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 106 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:58.304: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:58.304: Content-Type: audio/telephone-event

00 80 00 64

Jul 24 19:31:58.304: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DFFEB

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 107 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:58 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

..d

Jul 24 19:31:58.316: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8DFFEB

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 107 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:58.616: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:58.616: Content-Type: audio/telephone-event

03 00 07 D0

Jul 24 19:31:58.616: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8E02464

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 108 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:58 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 24 19:31:58.632: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8E02464

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 108 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:31:58.632: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 24 19:31:58.632: Content-Type: audio/telephone-event

03 80 00 64

Jul 24 19:31:58.632: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1191@172.20.100.20:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8E11702

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

To: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 109 NOTIFY

Max-Forwards: 70

Date: Wed, 24 Jul 2013 19:31:58 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:172.20.100.10:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.d

Jul 24 19:31:58.648: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.10:5060;branch=z9hG4bK8E11702

To: <sip:1191@172.20.100.20>;tag=cue626ca961

From: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 109 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: telephone-event

Allow-Events: message-summary

Jul 24 19:32:04.712: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:1103@172.20.100.10:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~169

Max-Forwards: 70

To: <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

From: <sip:1191@172.20.100.20>;tag=cue626ca961

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

CSeq: 1 BYE

Content-Length: 0

Contact: <sip:1191@172.20.100.20:5060>

Also: <sip:1103@172.20.100.10:5060;user=phone>

Jul 24 19:32:04.712: //2415/87BF34368A86/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~169

From: <sip:1191@172.20.100.20>;tag=cue626ca961

To: "Mike Hilty" <sip:1103@trunking.voipdnsservers.com>;tag=49D47EC-1F91

Date: Wed, 24 Jul 2013 19:32:04 GMT

Call-ID: 88956F6B-F3CE11E2-8A8BFDEF-396CC98A@172.20.100.10

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 BYE

P-RTP-Stat: PS=450,OS=72000,PR=300,OR=47523,PL=0,JI=0,LA=0,DU=9

Content-Length: 0

Everyone's tags (3)
5 REPLIES
New Member

Problems with CUE AA to CME extension.

Also, not sure if this helps or not, but all of the phones are SCCP phones (7940's)

The router is a 2821 running c2800nm-adventerprisek9-mz.151-4.M4.bin

The CUE is a AIM-CUE running Unity Express 3.2.2

The software versions are what came on the hardware platforms.  I have not updated either (trying to get by without a service contract on this hardware)

Thanks,

Mike Hilty

New Member

Problems with CUE AA to CME extension.

Turned out that adding "transfer-mode attended" under "ccn subsystem sip" on the NAM-CUE resolved this issue.  Not sure why this worked originally without this command, but now it is working properly.  Would like to understand why this is the case.

New Member

Problems with CUE AA to CME extension.

Another update:

Changing the transfer-mode in CUE gives different behavior depending on the setting:

transfer-mode attended:  Allows the caller to dial an extension in AA, and have it ring the extension.  However, when that extension rings through to voicemail, the caller hears the AA message where it would have been if they had just stayed on the line without a selection.  Caller is unable to leave a voicemail message for any ephone-dn's.

transfer-mode semi-attended:  Caller gets the AA prompts all over again after dailing an extension number.  AA script starts from the beginning

transfer-mode blind refer or bye-also:  Caller gets the recorded message "The subscriber you are trying to reach is unavailable, goodbye." then the call is dropped.

I am looking for a solution where the caller is able to dial by extension, and be able to leave a voicemail message for that extension. 

Hall of Fame Super Gold

Re: Problems with CUE AA to CME extension.

You trace below show that caller entered 1103, but then an external call was attempted to xxx, since you hidden numbers one cannot tell what is what. Possibly 1103 had CFA set to that number.

Jul 24 19:26:57.343: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:xxxxxxxxxx@172.20.100.10:5060 SIP/2.0

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~166

Max-Forwards: 70

To: <>xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

From: <1191>;tag=cue26a9e987

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

CSeq: 1 BYE

Content-Length: 0

Contact: <1191>

Also: <1103>

Jul 24 19:26:57.343: //2398/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 172.20.100.20:5060;branch=z9hG4bKaVwKPXymH1TKCGaU2g7LNg~~166

From: <1191>;tag=cue26a9e987

To: "WIRELESS CALLER" <>xxxxxxxxxx@trunking.voipdnsservers.com>;tag=4988818-EFE

Date: Wed, 24 Jul 2013 19:26:57 GMT

Call-ID: CF0F5D44-F3CD11E2-8A72FDEF-396CC98A@172.20.100.10

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 BYE

P-RTP-Stat: PS=681,OS=102096,PR=430,OR=68323,PL=0,JI=0,LA=0,DU=12

Content-Length: 0

Jul 24 19:26:57.351: //2397/CF0C4FE48A6C/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:xxxxxxxxxx@208.73.146.xx:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.10.12:5060;branch=z9hG4bK8AF1BEB

From: <5702665351>;tag=4988864-3B7

To: "WIRELESS CALLER"  ;tag=gK0911fe0e

Date: Wed, 24 Jul 2013 19:26:57 GMT

Call-ID: pcst13746940041508191241310@192.168.201.118

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

Min-SE:  1800

Cisco-Guid: 3473690596-4090302946-2322398703-0963430794

User-Agent: Cisco-SIPGateway/IOS-12.x

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

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1374694017

Contact:

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 253

v=0

o=CiscoSystemsSIP-GW-UserAgent 4827 3501 IN IP4 10.1.10.12

s=SIP Call

c=IN IP4 10.1.10.12

t=0 0

m=audio 19008 RTP/AVP 0 101

c=IN IP4 10.1.10.12

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendonly

New Member

Problems with CUE AA to CME extension.

The issue turned out to be related to the dial-peer configuration.

I previously only had one outbound SIP dial-peer that had a destination-pattern of .T

I configured dial-peers for ten digit, eleven digit, and 911 calling along with the .T dial peer, and now I am able to dial by extension/name out of the CUE AA.

436
Views
5
Helpful
5
Replies
CreatePlease to create content