Jump to content

ITSP trunk call voice problem


Ganesh
 Share

Recommended Posts

We have configured an ITSP trunk with version 2.1.2.2292. We use the eye beam soft phone and when we make an outbound call to a mobile number, the voice is not clear at both the end. The sound level varies and sometimes goes silent in between.

 

If we configure the same ITSP details directly on the eye beam soft phone and make calls, the voice is clear on both the side. Below is the logs captured from pbxnsip after making a call.

 

 

INVITE sip:0791394772@196.22.138.50;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-1408f7619cd8548827d78e33ae5c154f;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

To: <sip:0791394772@196.22.138.50;user=phone>

Call-ID: 2fc93bf3@pbx

CSeq: 6077 INVITE

Max-Forwards: 70

Contact: <sip:saar@10.0.0.3:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: Coral-PBX/2.1.2.2292

Content-Type: application/sdp

Content-Length: 329

 

v=0

o=- 23637 23637 IN IP4 10.0.0.3

s=-

c=IN IP4 10.0.0.3

t=0 0

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

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

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] 2008/01/09 07:43:29: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 407 Proxy Authentication Required

CSeq: 6077 INVITE

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-1408f7619cd8548827d78e33ae5c154f;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

Call-ID: 2fc93bf3@pbx

To: <sip:0791394772@196.22.138.50;user=phone>

Contact: <sip:196.22.138.50:5060;transport=udp>

Proxy-Authenticate: DIGEST realm="SIPKernel", nonce="119987513009121200901385001301"

Content-Length: 0

 

 

[8] 2008/01/09 07:43:29: Answer challenge with username saar

[9] 2008/01/09 07:43:29: Resolve destination 1004: udp 196.22.138.50 5060 udp:1

[9] 2008/01/09 07:43:29: SIP Tx udp:196.22.138.50:5060:

ACK sip:0791394772@196.22.138.50;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-1408f7619cd8548827d78e33ae5c154f;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

To: <sip:0791394772@196.22.138.50;user=phone>

Call-ID: 2fc93bf3@pbx

CSeq: 6077 ACK

Max-Forwards: 70

Content-Length: 0

 

 

[9] 2008/01/09 07:43:29: Resolve destination 1005: udp 196.22.138.50 5060 udp:1

[9] 2008/01/09 07:43:29: SIP Tx udp:196.22.138.50:5060:

INVITE sip:0791394772@196.22.138.50;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-624150fc7d273518ebfcb1fd665bded5;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

To: <sip:0791394772@196.22.138.50;user=phone>

Call-ID: 2fc93bf3@pbx

CSeq: 6078 INVITE

Max-Forwards: 70

Contact: <sip:saar@10.0.0.3:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: Coral-PBX/2.1.2.2292

Proxy-Authorization: Digest realm="SIPKernel",nonce="119987513009121200901385001301",response="23f8dae7d629300159a1ae5f6044f2ba",username="saar",uri="sip:0791394772@196.22.138.50;user=phone",algorithm=MD5

Content-Type: application/sdp

Content-Length: 329

 

v=0

o=- 23637 23637 IN IP4 10.0.0.3

s=-

c=IN IP4 10.0.0.3

t=0 0

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

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

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] 2008/01/09 07:43:29: Message repetition, packet dropped

[9] 2008/01/09 07:43:29: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 100 Trying

CSeq: 6078 INVITE

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-624150fc7d273518ebfcb1fd665bded5;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

Call-ID: 2fc93bf3@pbx

To: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

Contact: <sip:196.22.138.50:5060;transport=udp>

Content-Length: 0

 

 

[9] 2008/01/09 07:43:30: SIP Tr udp:10.0.0.15:16424:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-db6862615260667e-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=f751e86c

To: "0791394772" <sip:0791394772@10.0.0.3>;tag=526064e588

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 1 INVITE

Contact: <sip:1000@10.0.0.3:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: Coral-PBX/2.1.2.2292

Content-Type: application/sdp

Content-Length: 230

 

v=0

o=- 29175 29175 IN IP4 10.0.0.3

s=-

c=IN IP4 10.0.0.3

t=0 0

m=audio 50190 RTP/AVP 18 3 101

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2008/01/09 07:43:35: Last message repeated 3 times

 

[9] 2008/01/09 07:43:35: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 180 Ringing

CSeq: 6078 INVITE

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-624150fc7d273518ebfcb1fd665bded5;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

Call-ID: 2fc93bf3@pbx

To: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

Contact: <sip:196.22.138.50:5060;transport=udp>

Content-Type: application/sdp

Content-Length: 214

 

v=0

o=SIPKernel 9104 9104 IN IP4 196.22.138.50

s=VoipSIP

i=Audio Session

c=IN IP4 196.22.138.50

t=0 0

m=audio 8104 RTP/AVP 18 101

a=rtpmap:18 G729/8000/1

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

[6] 2008/01/09 07:43:35: Sending RTP for 2fc93bf3@pbx#31759 to 196.22.138.50:8104

[9] 2008/01/09 07:43:36: SIP Rx udp:10.0.0.13:62652:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-7b6526126720553d-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>

To: "1001"<sip:1001@10.0.0.3>

From: "1001"<sip:1001@10.0.0.3>;tag=501d5e76

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 247 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[7] 2008/01/09 07:43:36: 2fc93bf3@pbx#31759: RTP pass-through mode

[7] 2008/01/09 07:43:36: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.#526064e588: RTP pass-through mode

[9] 2008/01/09 07:43:36: Resolve destination 1006: aaaa udp 10.0.0.13 62652

[9] 2008/01/09 07:43:36: Resolve destination 1006: a udp 10.0.0.13 62652

[9] 2008/01/09 07:43:36: Resolve destination 1006: udp 10.0.0.13 62652

[9] 2008/01/09 07:43:36: SIP Tx udp:10.0.0.13:62652:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-7b6526126720553d-1--d87543-;rport=62652

From: "1001" <sip:1001@10.0.0.3>;tag=501d5e76

To: "1001" <sip:1001@10.0.0.3>;tag=2885c6ef51

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 247 REGISTER

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>;expires=30

Content-Length: 0

 

 

[9] 2008/01/09 07:43:37: SIP Tr udp:10.0.0.15:16424:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-db6862615260667e-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=f751e86c

To: "0791394772" <sip:0791394772@10.0.0.3>;tag=526064e588

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 1 INVITE

Contact: <sip:1000@10.0.0.3:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: Coral-PBX/2.1.2.2292

Content-Type: application/sdp

Content-Length: 230

 

v=0

o=- 29175 29175 IN IP4 10.0.0.3

s=-

c=IN IP4 10.0.0.3

t=0 0

m=audio 50190 RTP/AVP 18 3 101

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2008/01/09 07:43:44: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 200 OK

CSeq: 6078 INVITE

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-624150fc7d273518ebfcb1fd665bded5;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

Call-ID: 2fc93bf3@pbx

To: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

Contact: <sip:196.22.138.50:5060;transport=udp>

Content-Type: application/sdp

Content-Length: 214

 

v=0

o=SIPKernel 9104 9104 IN IP4 196.22.138.50

s=VoipSIP

i=Audio Session

c=IN IP4 196.22.138.50

t=0 0

m=audio 8104 RTP/AVP 18 101

a=rtpmap:18 G729/8000/1

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

[7] 2008/01/09 07:43:44: Call 2fc93bf3@pbx#31759: Clear last INVITE

[9] 2008/01/09 07:43:44: Resolve destination 1007: url sip:196.22.138.50:5060;transport=udp

[9] 2008/01/09 07:43:44: Resolve destination 1007: a udp 196.22.138.50 5060

[9] 2008/01/09 07:43:44: Resolve destination 1007: udp 196.22.138.50 5060

[9] 2008/01/09 07:43:44: SIP Tx udp:196.22.138.50:5060:

ACK sip:196.22.138.50:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-6926c804049b9f694033c5d4e21f496b;rport

From: "saar" <sip:saar@196.22.138.50>;tag=31759

To: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

Call-ID: 2fc93bf3@pbx

CSeq: 6078 ACK

Max-Forwards: 70

Contact: <sip:saar@10.0.0.3:5060;transport=udp>

Content-Length: 0

 

 

[7] 2008/01/09 07:43:44: Determine pass-through mode after receiving response

[9] 2008/01/09 07:43:44: Resolve destination 1008: aaaa udp 10.0.0.15 16424

[9] 2008/01/09 07:43:44: Resolve destination 1008: a udp 10.0.0.15 16424

[9] 2008/01/09 07:43:44: Resolve destination 1008: udp 10.0.0.15 16424

[9] 2008/01/09 07:43:44: SIP Tx udp:10.0.0.15:16424:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-db6862615260667e-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=f751e86c

To: "0791394772" <sip:0791394772@10.0.0.3>;tag=526064e588

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 1 INVITE

Contact: <sip:1000@10.0.0.3:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: Coral-PBX/2.1.2.2292

Content-Type: application/sdp

Content-Length: 230

 

v=0

o=- 29175 29175 IN IP4 10.0.0.3

s=-

c=IN IP4 10.0.0.3

t=0 0

m=audio 50190 RTP/AVP 18 3 101

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2008/01/09 07:43:44: SIP Rx udp:10.0.0.15:16424:

ACK sip:1000@10.0.0.3:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-ba44510fab5af176-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1000@10.0.0.15:16424>

To: "0791394772"<sip:0791394772@10.0.0.3>;tag=526064e588

From: "1000"<sip:1000@10.0.0.3>;tag=f751e86c

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 1 ACK

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:43:46: SIP Rx udp:10.0.0.15:16424:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-0945532bfc3a4d17-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>

To: "1000"<sip:1000@10.0.0.3>

From: "1000"<sip:1000@10.0.0.3>;tag=9167a83b

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 9 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:43:46: Resolve destination 1009: aaaa udp 10.0.0.15 16424

[9] 2008/01/09 07:43:46: Resolve destination 1009: a udp 10.0.0.15 16424

[9] 2008/01/09 07:43:46: Resolve destination 1009: udp 10.0.0.15 16424

[9] 2008/01/09 07:43:46: SIP Tx udp:10.0.0.15:16424:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-0945532bfc3a4d17-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=9167a83b

To: "1000" <sip:1000@10.0.0.3>;tag=21bd6102a2

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 9 REGISTER

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>;expires=30

Content-Length: 0

 

 

[9] 2008/01/09 07:43:56: SIP Rx udp:196.22.138.50:5060:

BYE sip:saar@196.22.138.50 SIP/2.0

CSeq: 2 BYE

Via: SIP/2.0/UDP 196.22.138.50:5060

From: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

Call-ID: 2fc93bf3@pbx

To: "saar" <sip:saar@196.22.138.50>;tag=31759

Content-Length: 0

 

 

[9] 2008/01/09 07:43:56: Resolve destination 1010: aaaa udp 196.22.138.50 5060

[9] 2008/01/09 07:43:56: Resolve destination 1010: a udp 196.22.138.50 5060

[9] 2008/01/09 07:43:56: Resolve destination 1010: udp 196.22.138.50 5060

[9] 2008/01/09 07:43:56: SIP Tx udp:196.22.138.50:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 196.22.138.50:5060

From: <sip:0791394772@196.22.138.50;user=phone>;tag=090138081250181628908105

To: "saar" <sip:saar@196.22.138.50>;tag=31759

Call-ID: 2fc93bf3@pbx

CSeq: 2 BYE

Contact: <sip:saar@10.0.0.3:5060;transport=udp>

User-Agent: Coral-PBX/2.1.2.2292

RTP-RxStat: Dur=27,Pkt=744,Oct=21992,Underun=0

RTP-TxStat: Dur=12,Pkt=1027,Oct=32864

Content-Length: 0

 

 

[7] 2008/01/09 07:43:56: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.#526064e588: Media-aware pass-through mode

[7] 2008/01/09 07:43:56: Other Ports: 1

[7] 2008/01/09 07:43:56: Call Port: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.#526064e588

[9] 2008/01/09 07:43:56: Resolve destination 1011: url sip:1000@10.0.0.15:16424

[9] 2008/01/09 07:43:56: Resolve destination 1011: udp 10.0.0.15 16424

[9] 2008/01/09 07:43:56: SIP Tx udp:10.0.0.15:16424:

BYE sip:1000@10.0.0.15:16424 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-c4f6822523688c8618a367b8e0fdcc38;rport

From: "0791394772" <sip:0791394772@10.0.0.3>;tag=526064e588

To: "1000" <sip:1000@10.0.0.3>;tag=f751e86c

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 29013 BYE

Max-Forwards: 70

Contact: <sip:1000@10.0.0.3:5060>

RTP-RxStat: Dur=27,Pkt=1353,Oct=43296,Underun=0

RTP-TxStat: Dur=12,Pkt=1055,Oct=31960

Content-Length: 0

 

 

[8] 2008/01/09 07:43:56: UDP: recvfrom receives ICMP message

[8] 2008/01/09 07:43:56: Last message repeated 5 times

 

[9] 2008/01/09 07:43:56: SIP Rx udp:10.0.0.15:16424:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK-c4f6822523688c8618a367b8e0fdcc38;rport=5060

Contact: <sip:1000@10.0.0.15:16424>

To: "1000"<sip:1000@10.0.0.3>;tag=f751e86c

From: "0791394772"<sip:0791394772@10.0.0.3>;tag=526064e588

Call-ID: 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 29013 BYE

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[7] 2008/01/09 07:43:56: Call 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.#526064e588: Clear last request

[5] 2008/01/09 07:43:56: BYE Response: Terminate 550a607f58021975MjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

[9] 2008/01/09 07:44:01: SIP Rx udp:10.0.0.13:62652:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-a7345a259756f601-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>

To: "1001"<sip:1001@10.0.0.3>

From: "1001"<sip:1001@10.0.0.3>;tag=501d5e76

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 248 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:44:01: Resolve destination 1012: aaaa udp 10.0.0.13 62652

[9] 2008/01/09 07:44:01: Resolve destination 1012: a udp 10.0.0.13 62652

[9] 2008/01/09 07:44:01: Resolve destination 1012: udp 10.0.0.13 62652

[9] 2008/01/09 07:44:01: SIP Tx udp:10.0.0.13:62652:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-a7345a259756f601-1--d87543-;rport=62652

From: "1001" <sip:1001@10.0.0.3>;tag=501d5e76

To: "1001" <sip:1001@10.0.0.3>;tag=2885c6ef51

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 248 REGISTER

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>;expires=30

Content-Length: 0

 

 

[9] 2008/01/09 07:44:11: SIP Rx udp:10.0.0.15:16424:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-2468435f8f5a3672-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>

To: "1000"<sip:1000@10.0.0.3>

From: "1000"<sip:1000@10.0.0.3>;tag=9167a83b

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 10 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:44:11: Resolve destination 1013: aaaa udp 10.0.0.15 16424

[9] 2008/01/09 07:44:11: Resolve destination 1013: a udp 10.0.0.15 16424

[9] 2008/01/09 07:44:11: Resolve destination 1013: udp 10.0.0.15 16424

[9] 2008/01/09 07:44:11: SIP Tx udp:10.0.0.15:16424:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-2468435f8f5a3672-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=9167a83b

To: "1000" <sip:1000@10.0.0.3>;tag=21bd6102a2

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 10 REGISTER

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>;expires=30

Content-Length: 0

 

 

[9] 2008/01/09 07:44:26: SIP Rx udp:10.0.0.13:62652:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-8b7c44235a4c1e4e-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>

To: "1001"<sip:1001@10.0.0.3>

From: "1001"<sip:1001@10.0.0.3>;tag=501d5e76

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 249 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:44:27: Resolve destination 1014: aaaa udp 10.0.0.13 62652

[9] 2008/01/09 07:44:27: Resolve destination 1014: a udp 10.0.0.13 62652

[9] 2008/01/09 07:44:27: Resolve destination 1014: udp 10.0.0.13 62652

[9] 2008/01/09 07:44:27: SIP Tx udp:10.0.0.13:62652:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.13:62652;branch=z9hG4bK-d87543-8b7c44235a4c1e4e-1--d87543-;rport=62652

From: "1001" <sip:1001@10.0.0.3>;tag=501d5e76

To: "1001" <sip:1001@10.0.0.3>;tag=2885c6ef51

Call-ID: bb215c3e211c864bYjQzOGMzODdjOTMxODJiMTYwOWYwZjVhNzMxZmE4ZTM.

CSeq: 249 REGISTER

Contact: <sip:1001@10.0.0.13:62652;rinstance=f68baada41ad778a>;expires=30

Content-Length: 0

 

 

[9] 2008/01/09 07:44:36: SIP Rx udp:10.0.0.15:16424:

REGISTER sip:10.0.0.3 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-dd651b05f47f042e-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>

To: "1000"<sip:1000@10.0.0.3>

From: "1000"<sip:1000@10.0.0.3>;tag=9167a83b

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 11 REGISTER

Expires: 3600

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

User-Agent: eyeBeam release 1003l stamp 30936

Content-Length: 0

 

 

[9] 2008/01/09 07:44:36: Resolve destination 1015: aaaa udp 10.0.0.15 16424

[9] 2008/01/09 07:44:36: Resolve destination 1015: a udp 10.0.0.15 16424

[9] 2008/01/09 07:44:36: Resolve destination 1015: udp 10.0.0.15 16424

[9] 2008/01/09 07:44:36: SIP Tx udp:10.0.0.15:16424:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.0.0.15:16424;branch=z9hG4bK-d87543-dd651b05f47f042e-1--d87543-;rport=16424

From: "1000" <sip:1000@10.0.0.3>;tag=9167a83b

To: "1000" <sip:1000@10.0.0.3>;tag=21bd6102a2

Call-ID: 7642170c5514751dMjQ2MjMxMDY0Nzg2NTAzOTIyZGYwYTdiZDZiN2EzZGU.

CSeq: 11 REGISTER

Contact: <sip:1000@10.0.0.15:16424;rinstance=7074b30abcbe0170>;expires=30

Content-Length: 0

Link to comment
Share on other sites

Eyebeam is using G.729 only and also on the PBXNSIP we have set G.729 as the first codec in settings and in trunk. How do we see if transcoding is taking place?

 

When eyebeam is directly configured with the ITSP details it is using G.729 and the voice is clear.

 

please check the top level settings for the PBX, I've learned from experience that any settings in the top level will supercede domain codec settings..

 

The best way that we confirm the codec is to capture packets and look into the SDP (session descriptor packet)

Below is a call that is negotiating Ulaw

Message body

Session Description Protocol

Session Description Protocol Version (v): 0

Owner/Creator, Session Id (o): - 4631 4631 IN IP4 208.64.32.55

Session Name (s): -

Connection Information ©: IN IP4 208.64.32.55

Time Description, active time (t): 0 0

Media Description, name and address (m): audio 57486 RTP/AVP 0 8 18 2 3 101 Media Attribute (a): rtpmap:0 pcmu/8000

Media Attribute (a): rtpmap:8 pcma/8000

Media Attribute (a): rtpmap:18 g729/8000

Media Attribute (a): fmtp:18 annexb=no

Media Attribute (a): rtpmap:2 g726-32/8000

Media Attribute (a): rtpmap:3 gsm/8000

Media Attribute (a): rtpmap:101 telephone-event/8000

Media Attribute (a): fmtp:101 0-16

Media Attribute (a): sendrecv

 

 

Followed by the same call with A law set in the Global Codec settings

 

Session Description Protocol

Session Description Protocol Version (v): 0

Owner/Creator, Session Id (o): - 34655 34655 IN IP4 208.64.32.55

Session Name (s): -

Connection Information ©: IN IP4 208.64.32.55

Time Description, active time (t): 0 0

Media Description, name and address (m): audio 64006 RTP/AVP 8 0 18 2 3 101

Media Attribute (a): rtpmap:8 pcma/8000

Media Attribute Fieldname: rtpmap

Media Format: 8

MIME Type: pcma

Media Attribute (a): rtpmap:0 pcmu/8000

Media Attribute Fieldname: rtpmap

Media Format: 0

MIME Type: pcmu

Media Attribute (a): rtpmap:18 g729/8000

Media Attribute Fieldname: rtpmap

Media Format: 18

MIME Type: g729

Media Attribute (a): fmtp:18 annexb=no

Media Attribute Fieldname: fmtp

Media Format: 18 [g729]

Media format specific parameters: annexb=no

Media Attribute (a): rtpmap:2 g726-32/8000

Media Attribute Fieldname: rtpmap

Media Format: 2

MIME Type: g726-32

Media Attribute (a): rtpmap:3 gsm/8000

Media Attribute Fieldname: rtpmap

Media Format: 3

MIME Type: gsm

Media Attribute (a): rtpmap:101 telephone-event/8000

Media Attribute Fieldname: rtpmap

Media Format: 101

MIME Type: telephone-event

Media Attribute (a): fmtp:101 0-16

Media Attribute Fieldname: fmtp

Media Format: 101 [telephone-event]

Media format specific parameters: 0-16

Media Attribute (a): sendrecv

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...