Jump to content

Soft phone and PBXNSIP on same server


Ganesh
 Share

Recommended Posts

We are using PBXNSIP version 2.1.2.2292 (Win32). On the same server we also have a Xlite soft phone registered to pbxnsip. If we use the Xlite soft phone and make any calls to the registered users in the domain (other soft phone/hard phone) we have one way voice. The Xlite on the server can hear the other person whereas the far end phone can hear nothing.

 

We also have an ITSP trunk registered. If the Xlite on server dials a call via the trunk then the same problem is observed. But the other registered users can dial out via the trunk with both side voice.

 

Also we tried installing many other soft phone on the same server and found the same problem in all of these. I have taken some traces while using Xlite. Is there any settings that we need to do in pbxnsip for this?

 

Regards

Ganesh

 

Log when making a call from extension to extension (User 103 is a Snom phone and User "ramesh" is Xlite on the pbxnsip server)

 

 

[7] 2007/12/18 19:28:29: SIP Rx udp:192.168.0.60:19566:

INVITE sip:103@192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:ramesh@192.168.0.60:19566>

To: "103"<sip:103@192.168.0.60>

From: "ramesh"<sip:ramesh@192.168.0.60>;tag=dd595a45

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

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

Content-Type: application/sdp

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 379

 

v=0

o=- 6 2 IN IP4 192.168.0.60

s=CounterPath eyeBeam 1.5

c=IN IP4 192.168.0.60

t=0 0

m=audio 24022 RTP/AVP 107 119 0 98 8 3 101

a=alt:1 1 : 601np1Zq 7CfgXpw3 192.168.0.60 24022

a=fmtp:101 0-15

a=rtpmap:107 BV32/16000

a=rtpmap:119 BV32-FEC/16000

a=rtpmap:98 iLBC/8000

a=rtpmap:101 telephone-event/8000

a=sendrecv

a=x-rtp-session-id:D32F29F6507A436BA882E0104A075D42

 

[7] 2007/12/18 19:28:29: UDP: Opening socket on port 51316

[7] 2007/12/18 19:28:29: UDP: Opening socket on port 51317

[8] 2007/12/18 19:28:29: Could not find a trunk (1 trunks)

[8] 2007/12/18 19:28:29: Using outbound proxy sip:192.168.0.60:19566;transport=udp because UDP packet source did not match the via header

[9] 2007/12/18 19:28:29: Resolve destination 239: udp 192.168.0.60 19566

[7] 2007/12/18 19:28:29: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

To: "103" <sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Content-Length: 0

 

 

[6] 2007/12/18 19:28:29: Sending RTP for 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f34e009586 to 192.168.0.60:24022

[7] 2007/12/18 19:28:29: Calling extension 103

[8] 2007/12/18 19:28:29: Play audio_moh/noise.wav

[7] 2007/12/18 19:28:29: UDP: Opening socket on port 52316

[7] 2007/12/18 19:28:29: UDP: Opening socket on port 52317

[9] 2007/12/18 19:28:29: Using outbound proxy sip:192.168.0.100:2051;transport=udp because of flow-label

[9] 2007/12/18 19:28:29: Resolve destination 240: url sip:192.168.0.100:2051;transport=udp

[9] 2007/12/18 19:28:29: Resolve destination 240: a udp 192.168.0.100 2051

[9] 2007/12/18 19:28:29: Resolve destination 240: udp 192.168.0.100 2051

[7] 2007/12/18 19:28:29: SIP Tx udp:192.168.0.100:2051:

INVITE sip:103@192.168.0.100:2051;line=x2ggtrtu SIP/2.0

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-60e499a96f93f754ca02be53bb684cb1;rport

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>

Call-ID: d121ccb4@pbx

CSeq: 22350 INVITE

Max-Forwards: 70

Contact: <sip:103@192.168.0.60: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

Alert-Info: <http://127.0.0.1/Bellcore-dr2>

Content-Type: application/sdp

Content-Length: 337

 

v=0

o=- 17074 17074 IN IP4 192.168.0.60

s=-

c=IN IP4 192.168.0.60

t=0 0

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

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[8] 2007/12/18 19:28:29: No codec available for sending

[8] 2007/12/18 19:28:29: Last message repeated 5 times

 

[7] 2007/12/18 19:28:29: SIP Rx udp:192.168.0.100:2051:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-60e499a96f93f754ca02be53bb684cb1;rport=5060

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>;tag=7baddda08p

Call-ID: d121ccb4@pbx

CSeq: 22350 INVITE

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1

Require: 100rel

RSeq: 1

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

Allow-Events: talk, hold, refer

Content-Length: 0

 

 

[9] 2007/12/18 19:28:29: Resolve destination 241: url sip:192.168.0.100:2051;transport=udp

[9] 2007/12/18 19:28:29: Resolve destination 241: a udp 192.168.0.100 2051

[9] 2007/12/18 19:28:29: Resolve destination 241: udp 192.168.0.100 2051

[7] 2007/12/18 19:28:29: SIP Tx udp:192.168.0.100:2051:

PRACK sip:103@192.168.0.100:2051;line=x2ggtrtu SIP/2.0

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-b761b4008d9786ce876bad446aadebef;rport

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>;tag=7baddda08p

Call-ID: d121ccb4@pbx

CSeq: 22351 PRACK

Max-Forwards: 70

Contact: <sip:103@192.168.0.60:5060;transport=udp>

RAck: 1 22350 INVITE

Content-Length: 0

 

 

[8] 2007/12/18 19:28:29: Play audio_en/ringback.wav

[9] 2007/12/18 19:28:29: Resolve destination 242: udp 192.168.0.60 19566

[7] 2007/12/18 19:28:29: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

To: "103" <sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 46519 46519 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 51316 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:28:29: SIP Rx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-b761b4008d9786ce876bad446aadebef;rport=5060

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>;tag=7baddda08p

Call-ID: d121ccb4@pbx

CSeq: 22351 PRACK

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1

Content-Length: 0

 

 

[7] 2007/12/18 19:28:29: Call d121ccb4@pbx#31875: Clear last request

[7] 2007/12/18 19:28:30: SIP Tr udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

To: "103" <sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 46519 46519 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 51316 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2007/12/18 19:28:31: Resolve destination 243: udp 192.168.0.60 19566

[7] 2007/12/18 19:28:31: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-447cf62245593400-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b7161e26

To: "ramesh" <sip:ramesh@192.168.0.60>;tag=3fac963c53

Call-ID: f86de0169c1ca839M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 27 REGISTER

Contact: <sip:ramesh@192.168.0.60:19566;rinstance=c8c83f035fd41b6b>;expires=30

Content-Length: 0

 

 

[7] 2007/12/18 19:28:31: SIP Tr udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

To: "103" <sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 46519 46519 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 51316 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:28:37: Last message repeated 3 times

 

[7] 2007/12/18 19:28:37: SIP Rx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-60e499a96f93f754ca02be53bb684cb1;rport=5060

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>;tag=7baddda08p

Call-ID: d121ccb4@pbx

CSeq: 22350 INVITE

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1

User-Agent: snom300/6.2.3

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

Allow-Events: talk, hold, refer

Supported: timer, 100rel, replaces, callerid

Content-Type: application/sdp

Content-Length: 208

 

v=0

o=root 596557810 596557811 IN IP4 192.168.0.100

s=call

c=IN IP4 192.168.0.100

t=0 0

m=audio 52416 RTP/AVP 0 101

a=rtpmap:0 pcmu/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:28:37: Call d121ccb4@pbx#31875: Clear last INVITE

[6] 2007/12/18 19:28:37: Sending RTP for d121ccb4@pbx#31875 to 192.168.0.100:52416

[9] 2007/12/18 19:28:37: Resolve destination 244: url sip:192.168.0.100:2051;transport=udp

[9] 2007/12/18 19:28:37: Resolve destination 244: a udp 192.168.0.100 2051

[9] 2007/12/18 19:28:37: Resolve destination 244: udp 192.168.0.100 2051

[7] 2007/12/18 19:28:37: SIP Tx udp:192.168.0.100:2051:

ACK sip:103@192.168.0.100:2051;line=x2ggtrtu SIP/2.0

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-ca52be328d00fa205a514e9f811bfd10;rport

From: <sip:ramesh@localhost>;tag=31875

To: <sip:103@localhost>;tag=7baddda08p

Call-ID: d121ccb4@pbx

CSeq: 22350 ACK

Max-Forwards: 70

Contact: <sip:103@192.168.0.60:5060;transport=udp>

Content-Length: 0

 

 

[7] 2007/12/18 19:28:37: Determine pass-through mode after receiving response

[9] 2007/12/18 19:28:37: Resolve destination 245: udp 192.168.0.60 19566

[7] 2007/12/18 19:28:37: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-2c5e6b2df10d7f03-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

To: "103" <sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 46519 46519 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 51316 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:28:37: d121ccb4@pbx#31875: RTP pass-through mode

[7] 2007/12/18 19:28:37: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f34e009586: RTP pass-through mode

[7] 2007/12/18 19:28:37: SIP Rx udp:127.0.0.1:19566:

ACK sip:ramesh@127.0.0.1:5060 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-b575cc7e1a6d2e7e-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:ramesh@192.168.0.60:19566>

To: "103"<sip:103@192.168.0.60>;tag=f34e009586

From: "ramesh"<sip:ramesh@192.168.0.60>;tag=dd595a45

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 ACK

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 0

 

 

[7] 2007/12/18 19:28:44: SIP Rx udp:192.168.0.100:2051:

REGISTER sip:192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-6w3274gh0yg9;rport

From: <sip:103@192.168.0.60>;tag=n6uiolqtqi

To: <sip:103@192.168.0.60>

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 727 REGISTER

Max-Forwards: 70

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1;q=1.0;+sip.instance="<urn:uuid:07d965bd-13ac-44bd-850c-348e275df5b6>"

User-Agent: snom300/6.2.3

Supported: gruu

Allow-Events: dialog

X-Real-IP: 192.168.0.100

WWW-Contact: <http://192.168.0.100:80>

WWW-Contact: <https://192.168.0.100:443>

Expires: 3600

Content-Length: 0

 

[9] 2007/12/18 19:28:44: Resolve destination 248: aaaa udp 192.168.0.100 2051

[9] 2007/12/18 19:28:44: Resolve destination 248: a udp 192.168.0.100 2051

[9] 2007/12/18 19:28:44: Resolve destination 248: udp 192.168.0.100 2051

[7] 2007/12/18 19:28:44: SIP Tx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-6w3274gh0yg9;rport=2051

From: <sip:103@192.168.0.60>;tag=n6uiolqtqi

To: <sip:103@192.168.0.60>;tag=4800e88943

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 727 REGISTER

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;expires=30

Content-Length: 0

 

 

[7] 2007/12/18 19:28:44: SIP Tr udp:196.22.138.50:5060:

REGISTER sip:196.22.138.50 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-c774233ab4ba1b144695093377037d99;rport

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

To: "saar" <sip:saar@196.22.138.50>

Call-ID: jsgyyugv@pbx

CSeq: 32678 REGISTER

Max-Forwards: 70

Contact: <sip:saar@192.168.0.60:5060;transport=udp;line=c20ad4d7>;+sip.instance="<urn:uuid:64067fb9-45eb-4556-9667-544a7143959e>"

User-Agent: Coral-PBX/2.1.2.2292

Expires: 3600

Content-Length: 0

 

 

[7] 2007/12/18 19:28:44: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 200 OK

CSeq: 32678 REGISTER

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-c774233ab4ba1b144695093377037d99;rport

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

Call-ID: jsgyyugv@pbx

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

Contact: <sip:saar@192.168.0.60:5060;transport=udp;line=c20ad4d7>;expires=600

Expires: 600

Content-Length: 0

 

 

[7] 2007/12/18 19:28:45: Last message repeated 2 times

[9] 2007/12/18 19:28:45: Message repetition, packet dropped

[7] 2007/12/18 19:28:50: SIP Rx udp:192.168.0.100:2051:

BYE sip:103@192.168.0.60:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-rqxhv3j2k6or;rport

From: <sip:103@localhost>;tag=7baddda08p

To: <sip:ramesh@localhost>;tag=31875

Call-ID: d121ccb4@pbx

CSeq: 1 BYE

Max-Forwards: 70

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1

User-Agent: snom300/6.2.3

RTP-RxStat: Total_Rx_Pkts=1,Rx_Pkts=1,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0

RTP-TxStat: Total_Tx_Pkts=609,Tx_Pkts=609,Remote_Tx_Pkts=0

Content-Length: 0

 

 

[9] 2007/12/18 19:28:50: Resolve destination 249: aaaa udp 192.168.0.100 2051

[9] 2007/12/18 19:28:50: Resolve destination 249: a udp 192.168.0.100 2051

[9] 2007/12/18 19:28:50: Resolve destination 249: udp 192.168.0.100 2051

[7] 2007/12/18 19:28:50: SIP Tx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-rqxhv3j2k6or;rport=2051

From: <sip:103@localhost>;tag=7baddda08p

To: <sip:ramesh@localhost>;tag=31875

Call-ID: d121ccb4@pbx

CSeq: 1 BYE

Contact: <sip:103@192.168.0.60:5060;transport=udp>

User-Agent: Coral-PBX/2.1.2.2292

RTP-RxStat: Dur=20,Pkt=611,Oct=105092,Underun=0

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

Content-Length: 0

 

 

[7] 2007/12/18 19:28:50: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f34e009586: Media-aware pass-through mode

[7] 2007/12/18 19:28:50: Other Ports: 1

[7] 2007/12/18 19:28:50: Call Port: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f34e009586

[9] 2007/12/18 19:28:50: Resolve destination 250: url sip:192.168.0.60:19566;transport=udp

[9] 2007/12/18 19:28:50: Resolve destination 250: a udp 192.168.0.60 19566

[9] 2007/12/18 19:28:50: Resolve destination 250: udp 192.168.0.60 19566

[7] 2007/12/18 19:28:50: SIP Tx udp:192.168.0.60:19566:

BYE sip:ramesh@192.168.0.60:19566 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-aa88b433b32ad38456e9ff0825b60115;rport

From: "103" <sip:103@192.168.0.60>;tag=f34e009586

To: "ramesh" <sip:ramesh@192.168.0.60>;tag=dd595a45

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 26814 BYE

Max-Forwards: 70

Contact: <sip:ramesh@127.0.0.1:5060>

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

RTP-TxStat: Dur=12,Pkt=1024,Oct=176128

Content-Length: 0

 

 

[8] 2007/12/18 19:28:50: UDP: recvfrom receives ICMP message

[8] 2007/12/18 19:28:50: Last message repeated 8 times

 

[7] 2007/12/18 19:28:50: SIP Rx udp:192.168.0.60:19566:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-aa88b433b32ad38456e9ff0825b60115;rport=5060;received=192.168.0.60

Contact: <sip:ramesh@192.168.0.60:19566>

To: "ramesh"<sip:ramesh@192.168.0.60>;tag=dd595a45

From: "103"<sip:103@192.168.0.60>;tag=f34e009586

Call-ID: 4f38cb7c8606c707M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 26814 BYE

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 0

 

Log when making call via the trunk

 

[7] 2007/12/18 19:26:52: SIP Rx udp:192.168.0.60:19566:

INVITE sip:00919845211130@192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:ramesh@192.168.0.60:19566>

To: "00919845211130"<sip:00919845211130@192.168.0.60>

From: "ramesh"<sip:ramesh@192.168.0.60>;tag=b913ea4c

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

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

Content-Type: application/sdp

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 379

 

v=0

o=- 6 2 IN IP4 192.168.0.60

s=CounterPath eyeBeam 1.5

c=IN IP4 192.168.0.60

t=0 0

m=audio 22884 RTP/AVP 107 119 0 98 8 3 101

a=alt:1 1 : gsMQreKs 3moaqBYA 192.168.0.60 22884

a=fmtp:101 0-15

a=rtpmap:107 BV32/16000

a=rtpmap:119 BV32-FEC/16000

a=rtpmap:98 iLBC/8000

a=rtpmap:101 telephone-event/8000

a=sendrecv

a=x-rtp-session-id:DA8FDBB20B25451B9A87DE0C6C8B22A5

 

[7] 2007/12/18 19:26:52: UDP: Opening socket on port 53564

[7] 2007/12/18 19:26:52: UDP: Opening socket on port 53565

[8] 2007/12/18 19:26:52: Could not find a trunk (1 trunks)

[8] 2007/12/18 19:26:52: Using outbound proxy sip:192.168.0.60:19566;transport=udp because UDP packet source did not match the via header

[9] 2007/12/18 19:26:52: Resolve destination 220: udp 192.168.0.60 19566

[7] 2007/12/18 19:26:52: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

To: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Content-Length: 0

 

 

[6] 2007/12/18 19:26:52: Sending RTP for 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0 to 192.168.0.60:22884

[5] 2007/12/18 19:26:52: Dialplan: Match 00919845211130@192.168.0.60 to <sip:00919845211130@196.22.138.50;user=phone> on trunk A

[8] 2007/12/18 19:26:52: Play audio_moh/noise.wav

[7] 2007/12/18 19:26:52: UDP: Opening socket on port 49168

[7] 2007/12/18 19:26:52: UDP: Opening socket on port 49169

[9] 2007/12/18 19:26:52: Resolve destination 221: url sip:196.22.138.50

[9] 2007/12/18 19:26:52: Resolve destination 221: udp 196.22.138.50 5060

[7] 2007/12/18 19:26:52: SIP Tx udp:196.22.138.50:5060:

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

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-665f681d3c90f17ddfddfb3529db6112;rport

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

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

Call-ID: d2066bdb@pbx

CSeq: 20107 INVITE

Max-Forwards: 70

Contact: <sip:saar@192.168.0.60: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: 337

 

v=0

o=- 12526 12526 IN IP4 192.168.0.60

s=-

c=IN IP4 192.168.0.60

t=0 0

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

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

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] 2007/12/18 19:26:52: Resolve destination 222: udp 192.168.0.60 19566

[7] 2007/12/18 19:26:52: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

To: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 40493 40493 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 53564 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:26:52: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 407 Proxy Authentication Required

CSeq: 20107 INVITE

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-665f681d3c90f17ddfddfb3529db6112;rport

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

Call-ID: d2066bdb@pbx

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

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

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

Content-Length: 0

 

 

[8] 2007/12/18 19:26:52: Answer challenge with username saar

[9] 2007/12/18 19:26:52: Resolve destination 223: udp 196.22.138.50 5060 udp:1

[7] 2007/12/18 19:26:52: SIP Tx udp:196.22.138.50:5060:

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

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-665f681d3c90f17ddfddfb3529db6112;rport

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

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

Call-ID: d2066bdb@pbx

CSeq: 20107 ACK

Max-Forwards: 70

Content-Length: 0

 

 

[9] 2007/12/18 19:26:52: Resolve destination 224: udp 196.22.138.50 5060 udp:1

[7] 2007/12/18 19:26:52: SIP Tx udp:196.22.138.50:5060:

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

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-a4035c314bba94546dbd700386f35af9;rport

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

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

Call-ID: d2066bdb@pbx

CSeq: 20108 INVITE

Max-Forwards: 70

Contact: <sip:saar@192.168.0.60: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="119798620318150335212564350251",response="331940e43344d33a983f786e8249bfab",username="saar",uri="sip:00919845211130@196.22.138.50;user=phone",algorithm=MD5

Content-Type: application/sdp

Content-Length: 337

 

v=0

o=- 12526 12526 IN IP4 192.168.0.60

s=-

c=IN IP4 192.168.0.60

t=0 0

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

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

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] 2007/12/18 19:26:52: Message repetition, packet dropped

[7] 2007/12/18 19:26:53: SIP Tr udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

To: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 40493 40493 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 53564 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:26:53: SIP Tr udp:196.22.138.50:5060:

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

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-a4035c314bba94546dbd700386f35af9;rport

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

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

Call-ID: d2066bdb@pbx

CSeq: 20108 INVITE

Max-Forwards: 70

Contact: <sip:saar@192.168.0.60: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="119798620318150335212564350251",response="331940e43344d33a983f786e8249bfab",username="saar",uri="sip:00919845211130@196.22.138.50;user=phone",algorithm=MD5

Content-Type: application/sdp

Content-Length: 337

 

v=0

o=- 12526 12526 IN IP4 192.168.0.60

s=-

c=IN IP4 192.168.0.60

t=0 0

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

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:26:53: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 100 Trying

CSeq: 20108 INVITE

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-a4035c314bba94546dbd700386f35af9;rport

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

Call-ID: d2066bdb@pbx

To: <sip:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

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

Content-Length: 0

 

 

[7] 2007/12/18 19:26:54: SIP Tr udp:192.168.0.60:19566:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

To: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 40493 40493 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 53564 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:26:58: Last message repeated 2 times

 

[7] 2007/12/18 19:26:58: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 180 Ringing

CSeq: 20108 INVITE

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-a4035c314bba94546dbd700386f35af9;rport

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

Call-ID: d2066bdb@pbx

To: <sip:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

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

Content-Type: application/sdp

Content-Length: 214

 

v=0

o=SIPKernel 7480 7480 IN IP4 196.22.138.50

s=VoipSIP

i=Audio Session

c=IN IP4 196.22.138.50

t=0 0

m=audio 6480 RTP/AVP 18 101

a=rtpmap:18 G729/8000/1

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

[6] 2007/12/18 19:26:58: Sending RTP for d2066bdb@pbx#10352 to 196.22.138.50:6480

[7] 2007/12/18 19:26:58: d2066bdb@pbx#10352: RTP pass-through mode

[7] 2007/12/18 19:26:58: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0: RTP pass-through mode

[7] 2007/12/18 19:26:58: Cannot pass through on d2066bdb@pbx#10352, falling back to transcoding

[7] 2007/12/18 19:26:58: SIP Rx udp:192.168.0.100:2051:

REGISTER sip:192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-fdxw5gc5pcl4;rport

From: <sip:103@192.168.0.60>;tag=1uegr33a4w

To: <sip:103@192.168.0.60>

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 720 REGISTER

Max-Forwards: 70

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1;q=1.0;+sip.instance="<urn:uuid:07d965bd-13ac-44bd-850c-348e275df5b6>"

User-Agent: snom300/6.2.3

Supported: gruu

Allow-Events: dialog

X-Real-IP: 192.168.0.100

WWW-Contact: <http://192.168.0.100:80>

WWW-Contact: <https://192.168.0.100:443>

Expires: 3600

Content-Length: 0

 

 

[9] 2007/12/18 19:26:58: Resolve destination 225: aaaa udp 192.168.0.100 2051

[9] 2007/12/18 19:26:58: Resolve destination 225: a udp 192.168.0.100 2051

[9] 2007/12/18 19:26:58: Resolve destination 225: udp 192.168.0.100 2051

[7] 2007/12/18 19:26:58: SIP Tx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-fdxw5gc5pcl4;rport=2051

From: <sip:103@192.168.0.60>;tag=1uegr33a4w

To: <sip:103@192.168.0.60>;tag=4800e88943

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 720 REGISTER

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;expires=30

Content-Length: 0

 

 

[7] 2007/12/18 19:27:00: SIP Rx udp:196.22.138.50:5060:

SIP/2.0 200 OK

CSeq: 20108 INVITE

Via: SIP/2.0/UDP 192.168.0.60:5060;branch=z9hG4bK-a4035c314bba94546dbd700386f35af9;rport

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

Call-ID: d2066bdb@pbx

To: <sip:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

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

Content-Type: application/sdp

Content-Length: 214

 

v=0

o=SIPKernel 7480 7480 IN IP4 196.22.138.50

s=VoipSIP

i=Audio Session

c=IN IP4 196.22.138.50

t=0 0

m=audio 6480 RTP/AVP 18 101

a=rtpmap:18 G729/8000/1

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

[7] 2007/12/18 19:27:00: Call d2066bdb@pbx#10352: Clear last INVITE

[9] 2007/12/18 19:27:00: Resolve destination 226: url sip:196.22.138.50:5060;transport=udp

[9] 2007/12/18 19:27:00: Resolve destination 226: a udp 196.22.138.50 5060

[9] 2007/12/18 19:27:00: Resolve destination 226: udp 196.22.138.50 5060

[7] 2007/12/18 19:27:00: 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 192.168.0.60:5060;branch=z9hG4bK-17ba2fc565a4ace690902774ab05aca3;rport

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

To: <sip:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

Call-ID: d2066bdb@pbx

CSeq: 20108 ACK

Max-Forwards: 70

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

Content-Length: 0

 

 

[7] 2007/12/18 19:27:00: Determine pass-through mode after receiving response

[7] 2007/12/18 19:27:00: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0: RTP pass-through mode

[7] 2007/12/18 19:27:00: Cannot pass through on d2066bdb@pbx#10352, falling back to transcoding

[9] 2007/12/18 19:27:00: Resolve destination 227: udp 192.168.0.60 19566

[7] 2007/12/18 19:27:00: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-e5063265dc5bc875-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

To: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 INVITE

Contact: <sip:ramesh@127.0.0.1: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: 233

 

v=0

o=- 40493 40493 IN IP4 127.0.0.1

s=-

c=IN IP4 127.0.0.1

t=0 0

m=audio 53564 RTP/AVP 0 8 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2007/12/18 19:27:00: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0: RTP pass-through mode

[7] 2007/12/18 19:27:00: Cannot pass through on d2066bdb@pbx#10352, falling back to transcoding

[7] 2007/12/18 19:27:00: SIP Rx udp:127.0.0.1:19566:

ACK sip:ramesh@127.0.0.1:5060 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-db22182ecb4efd5d-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:ramesh@192.168.0.60:19566>

To: "00919845211130"<sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

From: "ramesh"<sip:ramesh@192.168.0.60>;tag=b913ea4c

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 1 ACK

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 0

 

 

[7] 2007/12/18 19:27:13: SIP Rx udp:192.168.0.100:2051:

REGISTER sip:192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-yjx0mn5jvo7i;rport

From: <sip:103@192.168.0.60>;tag=p9p97gh4hq

To: <sip:103@192.168.0.60>

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 721 REGISTER

Max-Forwards: 70

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1;q=1.0;+sip.instance="<urn:uuid:07d965bd-13ac-44bd-850c-348e275df5b6>"

User-Agent: snom300/6.2.3

Supported: gruu

Allow-Events: dialog

X-Real-IP: 192.168.0.100

WWW-Contact: <http://192.168.0.100:80>

WWW-Contact: <https://192.168.0.100:443>

Expires: 3600

Content-Length: 0

 

 

[9] 2007/12/18 19:27:13: Resolve destination 228: aaaa udp 192.168.0.100 2051

[9] 2007/12/18 19:27:13: Resolve destination 228: a udp 192.168.0.100 2051

[9] 2007/12/18 19:27:13: Resolve destination 228: udp 192.168.0.100 2051

[7] 2007/12/18 19:27:13: SIP Tx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-yjx0mn5jvo7i;rport=2051

From: <sip:103@192.168.0.60>;tag=p9p97gh4hq

To: <sip:103@192.168.0.60>;tag=4800e88943

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 721 REGISTER

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;expires=30

Content-Length: 0

 

 

[7] 2007/12/18 19:27:15: SIP Rx udp:192.168.0.60:19566:

REGISTER sip:192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-1537da3e43635150-1--d87543-;rport

Max-Forwards: 70

Contact: <sip:ramesh@192.168.0.60:19566;rinstance=c8c83f035fd41b6b>

To: "ramesh"<sip:ramesh@192.168.0.60>

From: "ramesh"<sip:ramesh@192.168.0.60>;tag=b7161e26

Call-ID: f86de0169c1ca839M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 24 REGISTER

Expires: 3600

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

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 0

 

 

[9] 2007/12/18 19:27:15: Resolve destination 229: udp 192.168.0.60 19566

[7] 2007/12/18 19:27:15: SIP Tx udp:192.168.0.60:19566:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 127.0.0.1:19566;branch=z9hG4bK-d87543-1537da3e43635150-1--d87543-;rport=19566;received=192.168.0.60

From: "ramesh" <sip:ramesh@192.168.0.60>;tag=b7161e26

To: "ramesh" <sip:ramesh@192.168.0.60>;tag=3fac963c53

Call-ID: f86de0169c1ca839M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 24 REGISTER

Contact: <sip:ramesh@192.168.0.60:19566;rinstance=c8c83f035fd41b6b>;expires=30

Content-Length: 0

 

 

[8] 2007/12/18 19:27:22: Call d2066bdb@pbx#10352: Response does not correspond to open request

[7] 2007/12/18 19:27:28: SIP Rx udp:192.168.0.100:2051:

REGISTER sip:192.168.0.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-zipjemgo75gc;rport

From: <sip:103@192.168.0.60>;tag=83rjcqljkp

To: <sip:103@192.168.0.60>

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 722 REGISTER

Max-Forwards: 70

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;flow-id=1;q=1.0;+sip.instance="<urn:uuid:07d965bd-13ac-44bd-850c-348e275df5b6>"

User-Agent: snom300/6.2.3

Supported: gruu

Allow-Events: dialog

X-Real-IP: 192.168.0.100

WWW-Contact: <http://192.168.0.100:80>

WWW-Contact: <https://192.168.0.100:443>

Expires: 3600

Content-Length: 0

 

 

[9] 2007/12/18 19:27:29: Resolve destination 230: aaaa udp 192.168.0.100 2051

[9] 2007/12/18 19:27:29: Resolve destination 230: a udp 192.168.0.100 2051

[9] 2007/12/18 19:27:29: Resolve destination 230: udp 192.168.0.100 2051

[7] 2007/12/18 19:27:29: SIP Tx udp:192.168.0.100:2051:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.100:2051;branch=z9hG4bK-zipjemgo75gc;rport=2051

From: <sip:103@192.168.0.60>;tag=83rjcqljkp

To: <sip:103@192.168.0.60>;tag=4800e88943

Call-ID: 3c26700d704e-xosd8bhexi63@snom300-000413259865

CSeq: 722 REGISTER

Contact: <sip:103@192.168.0.100:2051;line=x2ggtrtu>;expires=30

Content-Length: 0

 

 

[7] 2007/12/18 19:27:29: 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:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

Call-ID: d2066bdb@pbx

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

Content-Length: 0

 

 

[9] 2007/12/18 19:27:29: Resolve destination 231: aaaa udp 196.22.138.50 5060

[9] 2007/12/18 19:27:29: Resolve destination 231: a udp 196.22.138.50 5060

[9] 2007/12/18 19:27:29: Resolve destination 231: udp 196.22.138.50 5060

[7] 2007/12/18 19:27:29: 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:00919845211130@196.22.138.50;user=phone>;tag=1812560715435499590786481

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

Call-ID: d2066bdb@pbx

CSeq: 2 BYE

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

User-Agent: Coral-PBX/2.1.2.2292

RTP-RxStat: Dur=37,Pkt=1312,Oct=41165,Underun=0

RTP-TxStat: Dur=30,Pkt=1,Oct=32

Content-Length: 0

 

 

[7] 2007/12/18 19:27:29: Other Ports: 1

[7] 2007/12/18 19:27:29: Call Port: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0

[9] 2007/12/18 19:27:29: Resolve destination 232: url sip:192.168.0.60:19566;transport=udp

[9] 2007/12/18 19:27:29: Resolve destination 232: a udp 192.168.0.60 19566

[9] 2007/12/18 19:27:29: Resolve destination 232: udp 192.168.0.60 19566

[7] 2007/12/18 19:27:29: SIP Tx udp:192.168.0.60:19566:

BYE sip:ramesh@192.168.0.60:19566 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-0948c2ede3dfbf173bd4cac072dee371;rport

From: "00919845211130" <sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

To: "ramesh" <sip:ramesh@192.168.0.60>;tag=b913ea4c

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 11604 BYE

Max-Forwards: 70

Contact: <sip:ramesh@127.0.0.1:5060>

RTP-RxStat: Dur=37,Pkt=0,Oct=0,Underun=588

RTP-TxStat: Dur=30,Pkt=1569,Oct=269244

Content-Length: 0

 

 

[8] 2007/12/18 19:27:29: UDP: recvfrom receives ICMP message

[8] 2007/12/18 19:27:29: Last message repeated 8 times

 

[7] 2007/12/18 19:27:29: SIP Rx udp:192.168.0.60:19566:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-0948c2ede3dfbf173bd4cac072dee371;rport=5060;received=192.168.0.60

Contact: <sip:ramesh@192.168.0.60:19566>

To: "ramesh"<sip:ramesh@192.168.0.60>;tag=b913ea4c

From: "00919845211130"<sip:00919845211130@192.168.0.60>;tag=f4b3c76df0

Call-ID: 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

CSeq: 11604 BYE

User-Agent: X-Lite release 1003l stamp 30942

Content-Length: 0

 

 

[7] 2007/12/18 19:27:29: Call 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.#f4b3c76df0: Clear last request

[5] 2007/12/18 19:27:29: BYE Response: Terminate 2412395977619005M2FlNjIwMmY4MTA3ZGNiNDgyNzFmN2I4YTQ4NmIxNTc.

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