Ganesh
-
Posts
47 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ganesh
-
-
Does pbxnsip support G 723.1 codec?
-
Hi
Can you please tell me what is the BHCC and BHCA values currently available in PBXnSIP? Our customer is using a dual core P4 server with 4 GB RAM.
Regards
Ganesh
-
How do we change the pbxnsip logo in Linux redhat and Suse? Can someone help?
-
We are installing pbxnsip in Linux Suse 9.2. I downloaded the file pbxctrl-suse10-2.1.6.2448. I checked the wiki on how to install in Linux but as we are not very familiar with Linux its all looking like greek to us.
I appreciate if someone could send me few steps on how to install pbxnsip in Suse. Maybe a step by step procedure after downloading and how to install will be really helpful.
The downloaded pbx file is for Suse 10 but we are using Suse 9.2. Is that ok or should we switch to Suse 10.x?
Regards
Ganesh
-
I created an IVR and added the default MoH file of PBXNSIP. From a registered user if i dial the IVR number the music is played continuously.
I configured a trunk (SIP gateway) in PBXNSIP and specified the incoming calls to land on IVR. From the FXS gateway (not registered to PBXNSIP) I was able to send the MOH request to PBXNSIP but the music is not played to the analog extensions. In the logs i see the request from the FXS gateway is forwarded to the IVR. Why is it not playing the music? Is there any other settings? The logs are attached.
-
Yes. I will use this account to send MOH request from the gateway to play music when the analog phones puts a call on hold.
-
I want to use the MOH of PBXnSIP to be played to the analog phones connected to a FXS gateway. The FXS gateway as a provision to use external MOH server for playing the music. It is not registered or configured as trunk with the PBXnSIP. In the gateway i specified the MOH URL as "moh.wav@IP address of pbxnsip" and see the gateway sending the request to PBXnSIP but says "not found". How do i create a MOH account in the PBXnSIP? Is this possible? Can i create an extension and point it to play a MOH for the gateway?
-
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.
-
We have version 2.1.2.2292 (Win32) which is installed in the LAN. The domain is created as "localhost". The LAN IP is natted to a public IP. Phones within the LAN are using the natted IP as registrar and getting registered to the PBX.
The phones outside the office are using this public IP to register. The phones at some office are registering with the PBX. But in the PBX trace for registered phones, we see Via: SIP/2.0/UDP 0.0.0.0:1040 and Contact: <sip:109@0.0.0.0:1040>. Is this normal? Why is it not displaying the IP address? Registered trace is given below.
But at some offices the phones are not registering. There is no firewall in the network. The customer also has a PBX on direct public IP at a different location. If they try registering the same phones to the PBX that is on direct IP it is registering. The same phones are not registering to natted IP. Below is the logs taken from the phone. What could be the problem?
Registered Trace:
EGISTER sip:192.168.200.72 SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:1040;branch=z9hG4bK-gjvoz3k3jdgd;rport
From: "109" <sip:109@220.225.222.166>;tag=yyb923olv1
To: "109" <sip:109@220.225.222.166>
Call-ID: 2bba85479fd5-0sqr7ku8a2pr@snomSoft
CSeq: 619 REGISTER
Max-Forwards: 70
Contact: <sip:109@0.0.0.0:1040;line=3tjczupg>;q=1.0;+sip.instance="<urn:uuid:1440620d-1019-4b4b-a6a1-770b02fe6a41>";audio;mobility="fixed";duplex="full";description="snomSoft";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
User-Agent: snomSoft/3.60j
Supported: gruu
Allow-Events: dialog
X-Real-IP: 0.0.0.0
Expires: 3600
Content-Length: 0
[9] 2008/01/10 00:01:45: Resolve destination 2090: udp 192.168.200.254 49083
[9] 2008/01/10 00:01:45: SIP Tx udp:192.168.200.254:49083:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 0.0.0.0:1040;branch=z9hG4bK-gjvoz3k3jdgd;rport=49083;received=192.168.200.254
From: "109" <sip:109@220.225.222.166>;tag=yyb923olv1
To: "109" <sip:109@220.225.222.166>;tag=30b628b6c0
Call-ID: 2bba85479fd5-0sqr7ku8a2pr@snomSoft
CSeq: 619 REGISTER
Contact: <sip:109@0.0.0.0:1040;line=3tjczupg>;expires=30
Content-Length: 0
Logs from phone not registering:
[5]10/1/2008 04:32:46: Opening UDP socket on port 0
[5]10/1/2008 04:32:46: Opening UDP socket on port 0
[5]10/1/2008 04:32:46: Opening UDP socket on port 0
[5]10/1/2008 04:32:46: Opening UDP socket on port 161
[5]10/1/2008 10:02:46: Opening TCP socket on port 0
[5]10/1/2008 10:02:46: Opening TCP socket on port 1800
[5]10/1/2008 10:02:46: Opening TCP socket on port 443
[5]10/1/2008 10:02:46: Opening UDP socket on port 0
[8]10/1/2008 10:02:46: Routing to outbound proxy sip:220.225.222.166
[8]10/1/2008 10:02:46: route_pending_packet 1000000: entry=url ? sip:220.225.222.166
[8]10/1/2008 10:02:46: route_pending_packet 1000000: entry=udp 220.225.222.166 5060
[8]10/1/2008 10:02:46: Send Packet REGISTER
[8]10/1/2008 10:02:46: Routing to outbound proxy sip:220.225.222.166
[8]10/1/2008 10:02:46: route_pending_packet 1000001: entry=url ? sip:220.225.222.166
[8]10/1/2008 10:02:46: route_pending_packet 1000001: entry=udp 220.225.222.166 5060
[7]10/1/2008 10:02:46: Trusted IP Addresses: udp:220.225.222.166
[5]10/1/2008 10:02:46: Opened audio
[8]10/1/2008 10:02:51: Send Packet REGISTER
[8]10/1/2008 10:02:52: Send Packet REGISTER
[8]10/1/2008 10:02:54: Send Packet REGISTER
[8]10/1/2008 10:02:58: Send Packet REGISTER
[8]10/1/2008 10:03:06: Send Packet REGISTER
[8]10/1/2008 10:03:22: Send Packet REGISTER
[2]10/1/2008 10:03:22: Registrar 104@220.225.222.166 timed out
[3]10/1/2008 10:03:36: DNS: Timeout on provisioning.snom.com
[8]10/1/2008 10:03:36: DNS Cache: Add a provisioning.snom.com = (ttl=60)
[8]10/1/2008 10:03:36: DNS cache_lookup: a provisioning.snom.com ->
[0]10/1/2008 10:03:36: Webclient: Could not find host provisioning.snom.com:80
[8]10/1/2008 10:03:36: DNS Cache: Add a 80 = (ttl=900)
[8]10/1/2008 10:04:22: Routing to outbound proxy sip:220.225.222.166
[8]10/1/2008 10:04:22: route_pending_packet 1000002: entry=url ? sip:220.225.222.166
[8]10/1/2008 10:04:22: route_pending_packet 1000002: entry=udp 220.225.222.166 5060
[8]10/1/2008 10:04:22: Send Packet REGISTER
[8]10/1/2008 10:04:22: Routing to outbound proxy sip:220.225.222.166
[8]10/1/2008 10:04:22: route_pending_packet 1000003: entry=url ? sip:220.225.222.166
[8]10/1/2008 10:04:22: route_pending_packet 1000003: entry=udp 220.225.222.166 5060
[7]10/1/2008 10:04:22: Trusted IP Addresses: udp:220.225.222.166
[8]10/1/2008 10:04:22: Send Packet REGISTER
[8]10/1/2008 10:04:23: Send Packet REGISTER
[8]10/1/2008 10:04:25: Send Packet REGISTER
[8]10/1/2008 10:04:29: Send Packet REGISTER
[8]10/1/2008 10:04:36: DNS Cache: Removing a provisioning.snom.com
[8]10/1/2008 10:04:37: Send Packet REGISTER
[8]10/1/2008 10:04:53: Send Packet REGISTER
[2]10/1/2008 10:04:53: Registrar 104@220.225.222.166 timed out
-
It is Windows.
-
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
-
Hi
We have a customer who is looking for integrating the address book of microsoft outlook with PBXNSIP such that they use the microsoft outlook to dial the call. They click on the address book and which then sends a dial out to PBXNSIP.
I belive another vendor as told the customer this is supported by their application. Is this possible with PBXNSIP?
Regards
Ganesh
-
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.
-
Our customer is using pbxnsip version 2.1.2.2292 (Win32). We added an ITSP trunk of a service provider. The trunk is not registering with pbxnsip. We see an error "408 Request Timeout" or "500 Address Resolution Failed". Instead of the ITSP domain name (sip99.telfreesa.com) we tried using its associated IP address in the "Trunk" "domain" settings but the trunk still does not register. Looks like this ITSP trunk (sip99.telfreesa.com) can only be registered using its domain name and not its IP address.
On the same pbxnsip server we have a X lite soft phone installed and if the X lite soft phone is configured with this ITSP details then it is registering using the domain name (sip99.telfreesa.com). If the problem is related to the DNS then even X lite must not register. Right?
Below is the logs from Xlite phone when the trunk is registered and from pbxnsip not registering
Session Initiation Protocol
Request-Line: REGISTER sip:ip99.telfreesa.com SIP/2.0
Sent-by Address: 10.10.10.95
Sent-by port: 8476
Contact: <sip:877510513@10.10.10.95:8476;rinstance=37db45eb1e3e2192>
SIP contact address: sip:877510513@10.10.10.95:8476
To: "877510513"<sip:877510513@ip99.telfreesa.com>
SIP Display info: "877510513"
SIP to address: sip:877510513@ip99.telfreesa.com
From: "877510513"<sip:877510513@ip99.telfreesa.com>;tag=35636f48
User-Agent: X-Lite release 1011s stamp 41150
Status-Line: SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.95:55116;branch=z9hG4bK-d87543-a714d3205d328f73-1--d87543-;rport=32995;received=41.208.212.7
Record-Route: <sip:infinet.4.1d8a2ec4.5070.citymoon@196.46.138.29:5060;lr>
Server: CityMoon SIP/1.6.1.001
User-Agent: CityMoon SIP/1.6.1.001
PBX Logs:
[9] 2007/12/14 10:09:40: Resolve destination 1: url sip:sip99.telfreesa.com
[9] 2007/12/14 10:09:40: Resolve destination 1: naptr sip99.telfreesa.com
[9] 2007/12/14 10:09:42: SIP Rx udp:10.10.10.95:47488:
[8] 2007/12/14 10:10:00: DNS: Add dns_naptr sip99.telfreesa.com (ttl=3600)
[9] 2007/12/14 10:10:00: Resolve destination 1: naptr sip99.telfreesa.com
[9] 2007/12/14 10:10:00: Resolve destination 1: srv tls _sips._tcp.sip99.telfreesa.com
5] 2007/12/14 10:10:10: Registration on trunk 12 (SIP_TRUNK_ITSP) failed. Retry in 60 seconds
[2] 2007/12/14 10:10:10: Trunk status SIP_TRUNK_ITSP (12) changed to "408 Request Timeout" (Registration failed, retry after 60 seconds)
[8] 2007/12/14 10:10:19: DNS: Add dns_srv _sips._tcp.sip99.telfreesa.com (ttl=3600)
[4] 2007/12/14 10:10:19: Could not find packet with number -1
Regards
Ganesh
-
We have installed PBXNSIP version 2.1.1 2201 (windows 32) on Windows Vista. When we make a call from one extension to other, there is no voice between them. The default firewall is disabled and no other application is installed in the system. If we dial a IVR number or conference, we can hear the recorded message from the system but not the voice between the users.
The same version is working fine if we replace the server with Windows XP machine. Is there any others settings in Vista to be changed?
Regards
Ganesh
-
This customer has the existing database in mysql and language of the intranet site is jsp. The fields shown in the screen correspond to the following table.field:
Company = aa_hierachy.countryCode
Department = aa_hierachy.deptCode
Section = aa_hierachy.sectionCode
Staff Number = aa_hierachy.staffNumber
Name = security_user.firstName
Office Direct Line = aa_hierachy.contactOfficeDirectLineNumber
Office Ext = aa_hierachy.contactOfficeGeneralNumber
Handphone = aa_hierachy.contactHpNumber
Email = security_user.email1
If we use TSP can get something like this with a "click to dial" added? or can this directory be integrated to 2.1 with click to dial? Basically the customer wants to use the existing database and is looking for application that can integrate and work with it.
-
Thanks. It worked
-
Are they using the domain name "localhost"?
They have domain (Private IP address) created for the phones in LAN to register but the domain "localhost" still exist without any users in it.
-
We have a customer who is running pbxnsip (Version 2.x) in LAN. He has natted the private IP to a public IP and opened the ports on firewall. The Snom SIP phone (on public IP) is trying to register to pbxnsip using the natted IP as registrar. We can see the register requests coming to pbxnsip and pbxnsip is giving an error "send packet 404" as below
Resolve destination 122033: a udp 210.212.206.117 5060
Resolve destination 122033: udp 210.212.206.117 5060
Send Packet 404
What does this indicate? The ports are open bi-directional. Still we dont see any request reaching the phone.
Regards
Ganesh Neelakantan
-
We have a VoIP gateway that does not support auto answer (the agent must answer the call without the phone ringing). Is it possible to get the auto answer feature on pbxnsip such that the gateway is registered with it and any incoming calls are directed to the pbxnsip which enables the auto answer and the sends the calls to the gateway and the agents start the conversation?
I think some devices are available that can setup a permanent call between an agent (on the telephony side) and a SIP queuing device. The agent will then just receive the call rather than having to answer, the SIP device will normally make this work using a series of SIP REFER messages to transfer the agent between the holding pool and a real call. Most call centre applications work like this. Can you tell me if this can be acheived by using pbxnsip?
Regards
Ganesh Neelakantan
-
Currently there is only an intranet directory database with our customer which contains their employees name and extension. They require a button next to the name so that when they click the button, pbxnsip will initiate the call for them. Meaning, pbxnsip will handshake both the caller (the person who clicks) and the other person (the name at the directory). We would like to know if you can design the click to call features for our client.
Regards
Ganesh Neelakantan
Block outgoing calls
in General Setup
Posted
Can we have a feature code and password to block the outgoing calls of the user? Each user will dial the feature code and enter the password to lock/unlock the phone.