Jump to content

One way speech


Ganesh
 Share

Recommended Posts

We have a setup running in which there is one way speech. For inbound calls via the trunk the far end person can hear the agent but the agent cannot hear any voice. Below is log. The firewall is open for UDP ports. Can you see if we need to do any configuration changes in Pbxnsip?

 

[9] 2009/07/24 14:46:25: SIP Rx udp:192.168.200.204:5060:

OPTIONS sip:201@192.168.200.204 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac608188397

Max-Forwards: 70

From: <sip:201@192.168.200.204>;tag=1c608184426

To: <sip:201@192.168.200.204>

Call-ID: 60818406411200020958@192.168.200.204

CSeq: 1 OPTIONS

Contact: <sip:201@192.168.200.204>

Supported: em,timer,replaces,path

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

User-Agent: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[9] 2009/07/24 14:46:25: Resolve 25: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:25: Resolve 25: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:25: Resolve 25: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:25: SIP Tx udp:192.168.200.204:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac608188397

From: <sip:201@192.168.200.204>;tag=1c608184426

To: <sip:201@192.168.200.204>;tag=094c02e6ea

Call-ID: 60818406411200020958@192.168.200.204

CSeq: 1 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

[9] 2009/07/24 14:46:35: Resolve 26: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 26: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 26: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 27: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 27: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 27: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 28: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 28: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 28: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 29: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 29: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 29: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: SIP Rx udp:216.52.221.144:51560:

INVITE sip:222@122.166.31.203:5060 SIP/2.0

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>

Date: Fri, 24 Jul 2009 09:12:45 GMT

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Supported: timer,replaces

Min-SE: 1800

Cisco-Guid: 4227719171-2003309022-3116105749-3332332504

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

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

CSeq: 101 INVITE

Max-Forwards: 70

Remote-Party-ID: <sip:2199612221@216.52.221.144>;party=calling;screen=no;privacy=off

Timestamp: 1248426765

Contact: <sip:2199612221@216.52.221.144:5060>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 676

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 3750 881 IN IP4 216.52.221.144

s=SIP Call

c=IN IP4 216.52.221.144

t=0 0

m=audio 16748 RTP/AVP 0 8 18 2 98 99 4 3 100 101

c=IN IP4 216.52.221.144

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:2 G726-32/8000

a=rtpmap:98 G726-24/8000

a=rtpmap:99 G726-16/8000

a=rtpmap:4 G723/8000

a=fmtp:4 bitrate=6.3;annexa=yes

a=rtpmap:3 GSM/8000

a=rtpmap:100 X-NSE/8000

a=fmtp:100 192-194,200-202

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=X-sqn:0

a=X-cap: 1 audio RTP/AVP 100

a=X-cpar: a=rtpmap:100 X-NSE/8000

a=X-cpar: a=fmtp:100 192-194,200-202

a=X-cap: 2 image udptl t38

 

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:36494

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:36495

[5] 2009/07/24 14:46:35: Identify trunk (IP address and DID match) 6

[9] 2009/07/24 14:46:35: Resolve 30: aaaa udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 30: a udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 30: udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: SIP Tx udp:216.52.221.144:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Content-Length: 0

 

 

[9] 2009/07/24 14:46:35: Resolve 31: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 31: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 31: udp 192.168.200.204 5060

[6] 2009/07/24 14:46:35: Sending RTP for FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8 to 216.52.221.144:16748

[5] 2009/07/24 14:46:35: Trunk 4 (not global) sends call to account 222 in domain localhost

[8] 2009/07/24 14:46:35: Play audio_moh/noise.wav

[7] 2009/07/24 14:46:35: Hunt Group 222: Moving to next stage

[7] 2009/07/24 14:46:35: Hunt group 222 called 1 registrations

[9] 2009/07/24 14:46:35: Resolve 32: aaaa udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 32: a udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 32: udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: SIP Tx udp:216.52.221.144:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Length: 0

 

 

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:61334

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:61335

[9] 2009/07/24 14:46:35: Resolve 33: url sip:202@192.168.200.204

[9] 2009/07/24 14:46:35: Resolve 33: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: SIP Tx udp:192.168.200.204:5060:

INVITE sip:202@192.168.200.204 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-2e80dbcdbced790202a8fddcc7404e19;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>

Call-ID: 4cc7ab93@pbx

CSeq: 20197 INVITE

Max-Forwards: 70

Contact: <sip:202@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Type: application/sdp

Content-Length: 341

 

v=0

o=- 8812 8812 IN IP4 192.168.200.203

s=-

c=IN IP4 192.168.200.203

t=0 0

m=audio 61334 RTP/AVP 0 8 18 9 2 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:9 g722/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2009/07/24 14:46:35: Resolve 34: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 34: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: Resolve 34: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: SIP Rx udp:192.168.200.204:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-2e80dbcdbced790202a8fddcc7404e19;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20197 INVITE

Supported: em,timer,replaces,path

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

Server: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[9] 2009/07/24 14:46:35: SIP Rx udp:192.168.200.204:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-2e80dbcdbced790202a8fddcc7404e19;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20197 INVITE

Contact: <sip:202@192.168.200.204>

Supported: em,timer,replaces,path

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

Require: 100rel

RSeq: 1

Server: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[9] 2009/07/24 14:46:35: Resolve 35: url sip:202@192.168.200.204

[9] 2009/07/24 14:46:35: Resolve 35: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:35: SIP Tx udp:192.168.200.204:5060:

PRACK sip:202@192.168.200.204 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-9292f13a6cf04f6e0080f17e70b421c3;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20198 PRACK

Max-Forwards: 70

Contact: <sip:202@192.168.200.203:5060;transport=udp>

RAck: 1 20197 INVITE

Content-Length: 0

 

 

[8] 2009/07/24 14:46:35: Play audio_en/ringback.wav

[9] 2009/07/24 14:46:35: SIP Rx udp:192.168.200.204:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-9292f13a6cf04f6e0080f17e70b421c3;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20198 PRACK

Contact: <sip:202@192.168.200.204>

Supported: em,timer,replaces,path

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

Server: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[7] 2009/07/24 14:46:35: Call 4cc7ab93@pbx#63556: Clear last request

[9] 2009/07/24 14:46:36: SIP Tr udp:216.52.221.144:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Length: 0

 

 

[9] 2009/07/24 14:46:39: Last message repeated 3 times

[9] 2009/07/24 14:46:39: Resolve 36: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:39: Resolve 36: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:39: Resolve 36: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:42: Resolve 37: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:42: Resolve 37: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:42: Resolve 37: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:43: SIP Tr udp:216.52.221.144:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Length: 0

 

 

[7] 2009/07/24 14:46:45: Hunt Group 222: Moving to next stage

[7] 2009/07/24 14:46:45: Hunt group 222 called 0 registrations

[9] 2009/07/24 14:46:46: Resolve 38: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:46: Resolve 38: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:46: Resolve 38: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:48: Resolve 39: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:46:48: Resolve 39: a udp 192.168.200.204 5060

[9] 2009/07/24 14:46:48: Resolve 39: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:51: SIP Tr udp:216.52.221.144:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Length: 0

 

 

[7] 2009/07/24 14:46:55: Hunt Group 222: Moving to next stage

[7] 2009/07/24 14:46:55: Hunt group 222 called 0 registrations

[9] 2009/07/24 14:46:57: SIP Rx udp:192.168.200.204:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-2e80dbcdbced790202a8fddcc7404e19;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20197 INVITE

Contact: <sip:202@192.168.200.204>

Supported: em,timer,replaces,path

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

Server: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Type: application/sdp

Content-Length: 237

 

v=0

o=AudiocodesGW 621288964 621288882 IN IP4 192.168.200.204

s=Phone-Call

c=IN IP4 192.168.200.204

t=0 0

m=audio 6010 RTP/AVP 0 101

a=rtpmap:0 pcmu/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

a=sendrecv

 

[7] 2009/07/24 14:46:57: Call 4cc7ab93@pbx#63556: Clear last INVITE

[7] 2009/07/24 14:46:57: Set packet length to 20

[6] 2009/07/24 14:46:57: Send codec=pcmu/8000 afrer answer

[6] 2009/07/24 14:46:57: Sending RTP for 4cc7ab93@pbx#63556 to 192.168.200.204:6010

[9] 2009/07/24 14:46:57: Resolve 40: url sip:202@192.168.200.204

[9] 2009/07/24 14:46:57: Resolve 40: udp 192.168.200.204 5060

[9] 2009/07/24 14:46:57: SIP Tx udp:192.168.200.204:5060:

ACK sip:202@192.168.200.204 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-7f9cab7579ac99c088a3ad09463ac6b3;rport

From: <sip:2199612221@localhost;user=phone>;tag=63556

To: <sip:222@localhost>;tag=1c621280194

Call-ID: 4cc7ab93@pbx

CSeq: 20197 ACK

Max-Forwards: 70

Contact: <sip:202@192.168.200.203:5060;transport=udp>

Content-Length: 0

 

 

[7] 2009/07/24 14:46:57: Determine pass-through mode after receiving response

[6] 2009/07/24 14:46:57: send codec=pcmu/8000

[9] 2009/07/24 14:46:57: Resolve 41: aaaa udp 216.52.221.144 5060

[9] 2009/07/24 14:46:57: Resolve 41: a udp 216.52.221.144 5060

[9] 2009/07/24 14:46:57: Resolve 41: udp 216.52.221.144 5060

[9] 2009/07/24 14:46:57: SIP Tx udp:216.52.221.144:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Type: application/sdp

Content-Length: 269

 

v=0

o=- 37660 37660 IN IP4 192.168.200.203

s=-

c=IN IP4 192.168.200.203

t=0 0

m=audio 36494 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2009/07/24 14:46:57: 4cc7ab93@pbx#63556: RTP pass-through mode

[7] 2009/07/24 14:46:57: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8: RTP pass-through mode

[9] 2009/07/24 14:46:58: SIP Tr udp:216.52.221.144:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Type: application/sdp

Content-Length: 269

 

v=0

o=- 37660 37660 IN IP4 192.168.200.203

s=-

c=IN IP4 192.168.200.203

t=0 0

m=audio 36494 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2009/07/24 14:47:05: Last message repeated 4 times

[9] 2009/07/24 14:47:05: Resolve 42: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 42: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 42: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 43: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 43: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 43: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 44: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 44: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 44: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 45: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 45: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 45: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 46: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 46: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 46: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 47: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 47: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:05: Resolve 47: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:08: Resolve 48: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:08: Resolve 48: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:08: Resolve 48: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:10: SIP Rx udp:192.168.200.204:5060:

OPTIONS sip:201@192.168.200.204 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac664470479

Max-Forwards: 70

From: <sip:201@192.168.200.204>;tag=1c664466501

To: <sip:201@192.168.200.204>

Call-ID: 664466140112000201043@192.168.200.204

CSeq: 1 OPTIONS

Contact: <sip:201@192.168.200.204>

Supported: em,timer,replaces,path

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

User-Agent: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[9] 2009/07/24 14:47:10: Resolve 49: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:10: Resolve 49: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:10: Resolve 49: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:10: SIP Tx udp:192.168.200.204:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac664470479

From: <sip:201@192.168.200.204>;tag=1c664466501

To: <sip:201@192.168.200.204>;tag=73dbbdce2f

Call-ID: 664466140112000201043@192.168.200.204

CSeq: 1 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

[9] 2009/07/24 14:47:12: Resolve 50: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:12: Resolve 50: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:12: Resolve 50: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:13: SIP Tr udp:216.52.221.144:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Type: application/sdp

Content-Length: 269

 

v=0

o=- 37660 37660 IN IP4 192.168.200.203

s=-

c=IN IP4 192.168.200.203

t=0 0

m=audio 36494 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2009/07/24 14:47:16: Resolve 51: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:16: Resolve 51: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:16: Resolve 51: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:18: Resolve 52: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:18: Resolve 52: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:18: Resolve 52: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:19: SIP Rx udp:192.168.200.204:5060:

BYE sip:202@192.168.200.203:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac675660303

Max-Forwards: 70

From: <sip:222@localhost>;tag=1c621280194

To: <sip:2199612221@localhost;user=phone>;tag=63556

Call-ID: 4cc7ab93@pbx

CSeq: 1 BYE

Contact: <sip:202@192.168.200.204>

Supported: em,timer,replaces,path

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

User-Agent: Audiocodes-Sip-Gateway-MP-124 FXS/v.4.60A.016.003

Content-Length: 0

 

 

[9] 2009/07/24 14:47:19: Resolve 53: aaaa udp 192.168.200.204 5060

[9] 2009/07/24 14:47:19: Resolve 53: a udp 192.168.200.204 5060

[9] 2009/07/24 14:47:19: Resolve 53: udp 192.168.200.204 5060

[9] 2009/07/24 14:47:19: SIP Tx udp:192.168.200.204:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.200.204;branch=z9hG4bKac675660303

From: <sip:222@localhost>;tag=1c621280194

To: <sip:2199612221@localhost;user=phone>;tag=63556

Call-ID: 4cc7ab93@pbx

CSeq: 1 BYE

Contact: <sip:202@192.168.200.203:5060;transport=udp>

User-Agent: SI-PBX/3.3.1.3177

RTP-RxStat: Dur=44,Pkt=1076,Oct=185072,Underun=0

RTP-TxStat: Dur=22,Pkt=1,Oct=172

Content-Length: 0

 

 

[7] 2009/07/24 14:47:19: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8: Media-aware pass-through mode

[7] 2009/07/24 14:47:19: Other Ports: 1

[7] 2009/07/24 14:47:19: Call Port: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8

[9] 2009/07/24 14:47:19: Resolve 54: url sip:2199612221@216.52.221.144:5060

[9] 2009/07/24 14:47:19: Resolve 54: udp 216.52.221.144 5060

[9] 2009/07/24 14:47:19: SIP Tx udp:216.52.221.144:5060:

BYE sip:2199612221@216.52.221.144:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 509 BYE

Max-Forwards: 70

Contact: <sip:222@192.168.200.203:5060;transport=udp>

RTP-RxStat: Dur=44,Pkt=0,Oct=0,Underun=0

RTP-TxStat: Dur=22,Pkt=1076,Oct=185072

Content-Length: 0

 

 

[9] 2009/07/24 14:47:19: SIP Tr udp:216.52.221.144:5060:

BYE sip:2199612221@216.52.221.144:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 509 BYE

Max-Forwards: 70

Contact: <sip:222@192.168.200.203:5060;transport=udp>

RTP-RxStat: Dur=44,Pkt=0,Oct=0,Underun=0

RTP-TxStat: Dur=22,Pkt=1076,Oct=185072

Content-Length: 0

 

 

[9] 2009/07/24 14:47:20: SIP Rx udp:216.52.221.144:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport;received=122.166.31.203

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Date: Fri, 24 Jul 2009 09:13:30 GMT

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

CSeq: 509 BYE

 

 

[7] 2009/07/24 14:47:20: Call FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8: Clear last request

[5] 2009/07/24 14:47:20: BYE Response: Terminate FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Link to comment
Share on other sites

1-Way Audio in almost all cases is the result of Firewalls, Routers, and Phone Firmware and or it's settings. PBXnSIP by nature would almost never have 1-way audio trouble otherwise.

 

What can you easily eliminate? Firewall, routers, or Phones?

Link to comment
Share on other sites

This call was never really got established (there was no ACK for 200 OK). There was no response from the Cisco-SIPGateway/IOS-12.x to any of the messages that the PBX sent (except for the response to BYE).

 

We have a setup running in which there is one way speech. For inbound calls via the trunk the far end person can hear the agent but the agent cannot hear any voice. Below is log. The firewall is open for UDP ports. Can you see if we need to do any configuration changes in Pbxnsip?

 

[9] 2009/07/24 14:46:35: SIP Rx udp:216.52.221.144:51560:

INVITE sip:222@122.166.31.203:5060 SIP/2.0

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>

Date: Fri, 24 Jul 2009 09:12:45 GMT

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Supported: timer,replaces

Min-SE: 1800

Cisco-Guid: 4227719171-2003309022-3116105749-3332332504

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

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

CSeq: 101 INVITE

Max-Forwards: 70

Remote-Party-ID: <sip:2199612221@216.52.221.144>;party=calling;screen=no;privacy=off

Timestamp: 1248426765

Contact: <sip:2199612221@216.52.221.144:5060>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 676

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 3750 881 IN IP4 216.52.221.144

s=SIP Call

c=IN IP4 216.52.221.144

t=0 0

m=audio 16748 RTP/AVP 0 8 18 2 98 99 4 3 100 101

c=IN IP4 216.52.221.144

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:2 G726-32/8000

a=rtpmap:98 G726-24/8000

a=rtpmap:99 G726-16/8000

a=rtpmap:4 G723/8000

a=fmtp:4 bitrate=6.3;annexa=yes

a=rtpmap:3 GSM/8000

a=rtpmap:100 X-NSE/8000

a=fmtp:100 192-194,200-202

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=X-sqn:0

a=X-cap: 1 audio RTP/AVP 100

a=X-cpar: a=rtpmap:100 X-NSE/8000

a=X-cpar: a=fmtp:100 192-194,200-202

a=X-cap: 2 image udptl t38

 

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:36494

[9] 2009/07/24 14:46:35: UDP: Opening socket on 0.0.0.0:36495

[5] 2009/07/24 14:46:35: Identify trunk (IP address and DID match) 6

[9] 2009/07/24 14:46:35: Resolve 30: aaaa udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 30: a udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: Resolve 30: udp 216.52.221.144 5060

[9] 2009/07/24 14:46:35: SIP Tx udp:216.52.221.144:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Content-Length: 0

.

.

.

.

 

[9] 2009/07/24 14:47:19: SIP Tx udp:216.52.221.144:5060:

BYE sip:2199612221@216.52.221.144:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 509 BYE

Max-Forwards: 70

Contact: <sip:222@192.168.200.203:5060;transport=udp>

RTP-RxStat: Dur=44,Pkt=0,Oct=0,Underun=0

RTP-TxStat: Dur=22,Pkt=1076,Oct=185072

Content-Length: 0

 

 

[9] 2009/07/24 14:47:19: SIP Tr udp:216.52.221.144:5060:

BYE sip:2199612221@216.52.221.144:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 509 BYE

Max-Forwards: 70

Contact: <sip:222@192.168.200.203:5060;transport=udp>

RTP-RxStat: Dur=44,Pkt=0,Oct=0,Underun=0

RTP-TxStat: Dur=22,Pkt=1076,Oct=185072

Content-Length: 0

 

 

[9] 2009/07/24 14:47:20: SIP Rx udp:216.52.221.144:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.200.203:5060;branch=z9hG4bK-4dd697b98164e15b1920a9b53fe2b4ea;rport;received=122.166.31.203

From: <sip:222@122.166.31.203>;tag=5577fa45a8

To: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

Date: Fri, 24 Jul 2009 09:13:30 GMT

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

CSeq: 509 BYE

 

 

[7] 2009/07/24 14:47:20: Call FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144#5577fa45a8: Clear last request

[5] 2009/07/24 14:47:20: BYE Response: Terminate FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

Link to comment
Share on other sites

[9] 2009/07/24 14:46:57: SIP Tx udp:216.52.221.144:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.52.221.144:5060;branch=z9hG4bK521724

From: <sip:2199612221@216.52.221.144>;tag=18D0EFC0-1B12

To: <sip:222@122.166.31.203>;tag=5577fa45a8

Call-ID: FC13D89C-776811DE-B2ADC16F-10A1CBE6@216.52.221.144

CSeq: 101 INVITE

Contact: <sip:222@192.168.200.203:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: SI-PBX/3.3.1.3177

Content-Type: application/sdp

Content-Length: 269

 

v=0

o=- 37660 37660 IN IP4 192.168.200.203

s=-

c=IN IP4 192.168.200.203

t=0 0

m=audio 36494 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

Try to ping "192.168.200.203" from "216.52.221.144". Does that work? If not, it might explain why the media does not arrive at the PBX.

 

Unless 216.52.221.144 has a session border functionality that can deal with non-routable IP addresses. You may try to enable the SBC functionality of the User-Agent "Cisco-SIPGateway/IOS-12.x", then it should be working fine.

 

Also see https://www.pbxnsipsupport.com/index.php?_m...&ratetype=1.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...