cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
291
Views
0
Helpful
2
Replies

One way audio using vpn

Ahmed Awida
Level 1
Level 1

Hi all, my colleague  has a router in his home with vpn connection to our HQ,he has also ip phone that is registering with our cucm.when he calls outside numbers for example pstn number he hears the person that he is talking to but the person can't hear him.

here is the debug of ccsip messages,note that our gateway is configured as CUBE and connects to sip provider.

213.X.X.X is the outside interface that connecting our gateway to the sip provider.

85.X.X.X is the sip provider ip

192.168.99.41 cucm.

Thanks in advance.

output:

Received:

INVITE sip:989032658500@213.X.X.X:5060 SIP/2.0

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK463d9e7ea30

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CUCM9.1

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

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence, kpml

Supported: X-cisco-srtp-fallback,X-cisco-original-called

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

Cisco-Guid: 0521969152-0000065536-0000000513-0694397120

Session-Expires:  1800

P-Asserted-Identity: <sip:2214@192.168.99.41>

Remote-Party-ID: <sip:2214@192.168.99.41>;party=calling;screen=yes;privacy=off

Contact: <sip:2214@192.168.99.41:5060;transport=tcp>

Max-Forwards: 70

Content-Length: 0

1293519: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK463d9e7ea30

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

CSeq: 101 INVITE

Allow-Events: kpml, telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

1293520: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:89032658500@85.X.X.X:5060 SIP/2.0

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F0619D8

Remote-Party-ID: <sip:74956385058@213.X.X.X>;party=calling;screen=yes;privacy=off

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>

Date: Mon, 20 May 2013 07:51:50 GMT

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

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

Min-SE:  1800

Cisco-Guid: 521969152-65536-513-694397120

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

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

CSeq: 101 INVITE

Timestamp: 1369036310

Contact: <sip:74956385058@213.X.X.X:5060>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 69

Session-Expires:  1800

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 274

v=0

o=CiscoSystemsSIP-GW-UserAgent 7788 4637 IN IP4 213.X.X.X

s=SIP Call

c=IN IP4 213.X.X.X

t=0 0

m=audio 16752 RTP/AVP 0 101 19

c=IN IP4 213.X.X.X

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=rtpmap:19 CN/8000

a=ptime:20

c2801(config)#

c2801(config)#

c2801(config)#

c2801(config)#

1293521: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 213.X.X.X;branch=z9hG4bK1F0619D8;received=213.X.X.X;rport=51828

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

CSeq: 101 INVITE

Server: MCN-SS

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

Supported: replaces

Contact: <sip:89032658500@85.X.X.X:5060>

Content-Length: 0

1293525: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F0619D8;received=213.X.X.X;rport=51828

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>;tag=as26770bff

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

CSeq: 101 INVITE

Server: MCN-SS

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

Supported: replaces

Contact: <sip:89032658500@85.X.X.X:5060>

Content-Type: application/sdp

Content-Length: 236

v=0

o=MCN-MEDIA-GW 1956161095 1956161095 IN IP4 85.X.X.X

s=MCN-MEDIA-GW

c=IN IP4 85.X.X.X

t=0 0

m=audio 25804 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendrecv

1293526: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 183 Session Progress

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK463d9e7ea30

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>;tag=B692A3F8-1F9A

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

CSeq: 101 INVITE

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

Allow-Events: kpml, telephone-event

Remote-Party-ID: <sip:89032658500@213.X.X.X>;party=called;screen=yes;privacy=off

Contact: <sip:989032658500@213.X.X.X:5060;transport=tcp>

Call-Info: <sip:213.X.X.X:5060>;method="NOTIFY;Event=telephone-event;Duration=500"

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 3272 1018 IN IP4 213.X.X.X

c=IN IP4 213.X.X.X

t=0 0

m=audio 16928 RTP/AVP 0 101

c=IN IP4 213.X.X.X

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

1293530: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F0619D8;received=213.X.X.X;rport=51828

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>;tag=as26770bff

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X       

CSeq: 101 INVITE

Server: MCN-SS

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

Supported: replaces

Contact: <sip:89032658500@85.X.X.X:5060>

Content-Type: application/sdp

Content-Length: 236

v=0

o=MCN-MEDIA-GW 1956161095 1956161096 IN IP4 85.X.X.X

s=MCN-MEDIA-GW

c=IN IP4 85.X.X.X

t=0 0

m=audio 25804 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendrecv

1293531: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK463d9e7ea30

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>;tag=B692A3F8-1F9A

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

CSeq: 101 INVITE

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

Allow-Events: kpml, telephone-event

Remote-Party-ID: <sip:89032658500@213.X.X.X>;party=called;screen=no;privacy=off

Contact: <sip:89032658500@213.X.X.X:5060;transport=tcp>

Supported: replaces

Call-Info: <sip:213.X.X.X:5060>;method="NOTIFY;Event=telephone-event;Duration=500"

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 3272 1018 IN IP4 213.X.X.X

s=SIP Call

c=IN IP4 213.X.X.X

t=0 0

m=audio 16928 RTP/AVP 0 101

c=IN IP4 213.X.X.X

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

1293532: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:89032658500@85.X.X.X:5060 SIP/2.0

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F062591

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>;tag=as26770bff

Date: Mon, 20 May 2013 07:51:50 GMT

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

1293533: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:89032658500@213.X.X.X:5060;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK463e362b5df6

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>;tag=B692A3F8-1F9A

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: presence, kpml

Content-Type: application/sdp

Content-Length: 239

v=0

o=CiscoSystemsCCM-SIP 82870 1 IN IP4 192.168.99.41

s=SIP Call

c=IN IP4 192.168.157.10

b=TIAS:64000

b=AS:64

t=0 0

m=audio 32612 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=ptime:20

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

1293538: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:89032658500@213.X.X.X:5060;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK4640463864c0

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>;tag=B692A3F8-1F9A

Date: Mon, 20 May 2013 07:51:49 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

User-Agent: Cisco-CUCM9.1

Max-Forwards: 70

P-Asserted-Identity: <sip:2214@192.168.99.41>

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

1293539: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/TCP 192.168.99.41:5060;branch=z9hG4bK4640463864c0

From: <sip:2214@192.168.99.41>;tag=82870~bb7f7ca1-8833-4f33-919e-af49f25af5bb-50265431

To: <sip:989032658500@213.X.X.X>;tag=B692A3F8-1F9A

Date: Mon, 20 May 2013 07:52:05 GMT

Call-ID: 1f1c9e00-1991d615-3aba-2963a8c0@192.168.99.41

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

1293540: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:89032658500@85.X.X.X:5060 SIP/2.0

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F0631066

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>;tag=as26770bff

Date: Mon, 20 May 2013 07:51:50 GMT

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

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

Max-Forwards: 70

Timestamp: 1369036325

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

1293541: 5w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.X.X.X:5060;branch=z9hG4bK1F0631066;received=213.X.X.X;rport=51828

From: <sip:74956385058@192.168.99.41>;tag=B692917C-F78

To: <sip:89032658500@85.X.X.X>;tag=as26770bff

Call-ID: F684B2A2-C05811E2-B86FA49C-E0C2BAEE@213.X.X.X

CSeq: 102 BYE

Server: MCN-SS

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

Supported: replaces

Content-Length: 0

2 Replies 2

paolo bevilacqua
Hall of Fame
Hall of Fame

Check you VPN setup for access-list, firewall, or routing issue that prevents media packet from getting to the gateway.

That is ideally done by a qualified and/or certified Cisco engineer.

Hi Ahmed.

It depends on many factors:

routing ,as Paolo mentioned, sip trunk configuration between your CUCM and CUBE, codecs,NAT.

I also have a VPN between my home and HQ, I can correctly call inside and outside the HQ.

Please verifiy all possible misconfiguration

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: