Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

SIP Proxy and Media Proxy - Pre-Sales Technical Support
 LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support
Subject Topic: Call Routing Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
mgonenc
Intermediate
Intermediate


Joined: October 15 2007
Location: Turkey
Posts: 4
Posted: October 15 2007 at 8:19pm | IP Logged Quote mgonenc
Hi,

I want to route all calls to a specific IP.

I made the configurations at Call Routing section; "User Name as [0-9]+" and "Route List as x.x.x.x:5060"

When I make a call through Eyebeam which is installed on my computer, I got SIP Response "404 Not Found"

When I change User Name as the called number, it works without any problem.

It doesn't work when I use regular expressions. What should I write to this field for all calls to be routed to the specified address?

Thanks,
Mete
Back to Top View mgonenc's Profile Search for other posts by mgonenc
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 16 2007 at 6:46am | IP Logged Quote support
Hi Mete,

I think you may want to try a regular expression something like:

^[0-9]+$ for your IP:port destination of x.x.x.x:5060.

When you define regular expressions for routing, also make sure to use the "Test" button in the "Edit call routing information" dialog to see if your regular expression does what you want.

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
mgonenc
Intermediate
Intermediate


Joined: October 15 2007
Location: Turkey
Posts: 4
Posted: October 16 2007 at 7:19am | IP Logged Quote mgonenc
Hi Support,

I have also tried that, but it doesn't work either.

When I use the "Test" button, I can see that it routes. But when I send the call from Eyebeam, it fails with the code "404 Not Found"
Back to Top View mgonenc's Profile Search for other posts by mgonenc
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 16 2007 at 10:34am | IP Logged Quote support
Mete,

Post a SIP log from the proxy to this thread and we will take a look at what is happening.

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
mgonenc
Intermediate
Intermediate


Joined: October 15 2007
Location: Turkey
Posts: 4
Posted: October 16 2007 at 11:07am | IP Logged Quote mgonenc
Code:

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.11.200:10122) <<<<
INVITE sip:905322744114@192.168.11.200 SIP/2.0
To: <sip:905322744114@192.168.11.200>
From: mete<sip:001@192.168.11.200>;tag=1e57a20f
Via: SIP/2.0/UDP 192.168.11.200:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-
;rport
Call-ID: 141f573e2366530b
CSeq: 1 INVITE
Contact: <sip:001@192.168.11.200:10122>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF
O
Content-Type: application/sdp
User-Agent: eyeBeam release 3004t stamp 16741
Content-Length: 237

v=0
o=- 25379955 25379974 IN IP4 192.168.11.200
s=eyeBeam
c=IN IP4 192.168.11.200
t=0 0
m=audio 8180 RTP/AVP 18 101
a=alt:1 1 : 1DC7BC9E 0A9C468A 192.168.11.200 8180
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.11.200:10122) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.11.200:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-
;rport=10122;received=192.168.11.200
From: mete <sip:001@192.168.11.200>;tag=1e57a20f
To: <sip:905322744114@192.168.11.200>
Call-ID: 141f573e2366530b
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.11.200:10122) >>>>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.11.200:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-
;rport=10122;received=192.168.11.200
From: mete <sip:001@192.168.11.200>;tag=1e57a20f
To: <sip:905322744114@192.168.11.200>
Call-ID: 141f573e2366530b
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.11.200:10122) <<<<
ACK sip:905322744114@192.168.11.200 SIP/2.0
To: <sip:905322744114@192.168.11.200>
From: mete<sip:001@192.168.11.200>;tag=1e57a20f
Via: SIP/2.0/UDP 192.168.11.200:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-
;rport
Call-ID: 141f573e2366530b
CSeq: 1 ACK
Content-Length: 0

Back to Top View mgonenc's Profile Search for other posts by mgonenc
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 16 2007 at 1:13pm | IP Logged Quote support
We took your INVITE message from the Xten/Counterpath soft phone and sent it directly to a proxy here and received the same results. Obviously there is something in the INVITE message coming from the Xten that is causing grief. We will have to look into this. The last time we tested using Xten SIP products, all was OK.

Just so you can see that call route forwarding does work, we used another soft phone we have here that is based on the VOIP Media Engine and tested your setup. We tested both regular expression definitions of [0-9]+ and ^[0-9]+$ - both worked as expected.

As I mentioned, we will have to look into this. Will try to resolve the issue this week. Let us know if you want an updated product image for test.

SIP log using your call routing:
Code:

************* Log Opened (Oct 16 13:06:23) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:905322744114@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK00391bf3
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@ps>
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 3717671 3717671 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20000 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK00391bf3;received= 192.168.1.2
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@ps>
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5094) >>>>
INVITE sip:905322744114@192.168.1.80:5094 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf8877fa30576ee4e012c006ef4966 2510.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK00391bf3;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
max-forwards: 69
organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-customheader-extension-333: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   221

v=0
o=333 3717671 3717671 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20000 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf8877fa3 0576ee4e012c006ef49662510.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.4.8 (www.LanScapeCorp.com)
Content-Length: 0






<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf8877fa3 0576ee4e012c006ef49662510.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.4.8 (www.LanScapeCorp.com)
Content-Length: 0






>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
x-customheader-extension-111: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf8877fa3 0576ee4e012c006ef49662510.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
Record-Route: <sip:192.168.1.2>
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-Id: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
Contact: <sip:111@192.168.1.80:5094>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.4.8 (www.LanScapeCorp.com)
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 175
Content-Type: application/sdp

v=0
o=LanScape 3401546573 3401546573 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 8646 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
Record-Route: <sip:192.168.1.2>
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 INVITE
Contact: <sip:111@192.168.1.80:5094>
x-customheader-extension-111: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   175

v=0
o=LanScape 3401546573 3401546573 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 8646 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:905322744114@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-Id: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:111@192.168.1.80:5094>
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5094) >>>>
ACK sip:111@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKl8877fa30576ee4e012c006ef4966 2510
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00391bf3
Route: <sip:111@192.168.1.80:5094>
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741406 ACK
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
BYE sip:111@192.168.1.80:5094 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0038db0a
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-Id: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741407 BYE
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:111@192.168.1.80:5094>
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5094) >>>>
BYE sip:111@192.168.1.80:5094 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf34d76f5b7782e1bccf91c1f1118b 3d9f.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0038db0a;received= 192.168.1.2
Route: <sip:111@192.168.1.80:5094>
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741407 BYE
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf34d76f5 b7782e1bccf91c1f1118b3d9f.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0038db0a
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-Id: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741407 BYE
User-Agent: LanScape VOIP Media Engine/5.12.4.8 (www.LanScapeCorp.com)
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0038db0a
From: "Test Phone" <sip:333@ps>;tag=391428;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:905322744114@192.168.1.80:5094>;tag=16d9f47
Call-ID: aaa96cbb-33a8-4b4d-a582-a4d9bf530ab8-00000dd8@192.168.1.2
CSeq: 3741407 BYE
x-customheader-extension-111: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

************* Log Closed (Oct 16 13:07:00) *************



Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
mgonenc
Intermediate
Intermediate


Joined: October 15 2007
Location: Turkey
Posts: 4
Posted: October 16 2007 at 1:53pm | IP Logged Quote mgonenc
For you to know, I have also tested with Linksys PAP2T and had the same result "404 Not Found"

So I don't think it is a specific problem just with XTen.

Yes it will be good to have an updated product image for test.

Thanks,
Back to Top View mgonenc's Profile Search for other posts by mgonenc
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 16 2007 at 2:51pm | IP Logged Quote support
Thanks for the info. That really sucks. Post the SIP log for the PAP2T device also. We will look at this as soon as we can. we just migrated all code bases over to VS2005 sp1. Maybe we broke something.

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 19 2007 at 11:44am | IP Logged Quote support

Ok, we have an updated EXE image you can try. Send an email to support 'at' lanscapecorp.com if you want it. We will send it to you in a ZIP file.

Here is a log using your original INVITE SIP mesage from the xten phone. We only changed IP addresses in the original INVITE to make our test function. Because we do not haveyour specific version of xten phone, you will see that the final INVITE ACK is not present in the proxy sip log below.

We also used a call routing entry of [0-9]+ that forwarded calls to 192.168.1.80:5094.


Code:

************* Log Opened (Oct 19 11:33:43) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:1437) <<<<
INVITE sip:905322744114@192.168.1.140 SIP/2.0
To: <sip:905322744114@192.168.1.140>
From: mete<sip:001@192.168.1.140>;tag=1e57a20f
Via: SIP/2.0/UDP 192.168.1.140:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-;rport
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
Contact: <sip:001@192.168.1.140:10122>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 3004t stamp 16741
Content-Length: 237

v=0
o=- 25379955 25379974 IN IP4 192.168.1.140
s=eyeBeam
c=IN IP4 192.168.1.140
t=0 0
m=audio 8180 RTP/AVP 18 101
a=alt:1 1 : 1DC7BC9E 0A9C468A 192.168.1.140 8180
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv






>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:1437) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.140:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-;rport=1437;received=192.168.1.2
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.140>
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.2.6 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5094) >>>>
INVITE sip:905322744114@192.168.1.80:5094 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bKf03960f732b7a47884a21678b15 3ddd21.0
Via: SIP/2.0/UDP 192.168.1.140:10122;branch=z9hG4bK-d87543-723677665-1--d875 43-;rport=1437;received=192.168.1.2
Record-Route: <sip:192.168.1.140:5060;lr>
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
Contact: <sip:001@192.168.1.140:10122>
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.2.6 (www.LanScapeCorp.com)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Content-Length:   238

v=0
o=- 25379955 25379974 IN IP4 192.168.1.140
s=eyeBeam
c=IN IP4 192.168.1.140
t=0 0
m=audio 8180 RTP/AVP 18 101
a=alt:1 1 : 1DC7BC9E 0A9C468A 192.168.1.140 8180
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv






<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.140:5060;received=192.168.1.140;branch=z9hG4bKf039 60f732b7a47884a21678b153ddd21.0
Via: SIP/2.0/UDP 192.168.1.140:10122;received=192.168.1.2;rport=1437;branch=z 9hG4bK-d87543-723677665-1--d875 43-
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
Content-Length: 0






<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.140:5060;received=192.168.1.140;branch=z9hG4bKf039 60f732b7a47884a21678b153ddd21.0
Via: SIP/2.0/UDP 192.168.1.140:10122;received=192.168.1.2;rport=1437;branch=z 9hG4bK-d87543-723677665-1--d875 43-
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>;tag=1077c6e
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
Content-Length: 0






>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:1437) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.140:10122;received=192.168.1.2;rport=1437;branch=z 9hG4bK-d87543-723677665-1--d875 43-
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>;tag=1077c6e
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
x-customheader-extension-111: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.6 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5094) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.140:5060;received=192.168.1.140;branch=z9hG4bKf039 60f732b7a47884a21678b153ddd21.0
Via: SIP/2.0/UDP 192.168.1.140:10122;received=192.168.1.2;rport=1437;branch=z 9hG4bK-d87543-723677665-1--d875 43-
Record-Route: <sip:192.168.1.140>
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>;tag=1077c6e
Call-Id: 141f573e2366530b123
CSeq: 1 INVITE
Contact: <sip:111@192.168.1.80:5094>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.4.10 (www.LanScapeCorp.com)
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 175
Content-Type: application/sdp

v=0
o=LanScape 2147483647 2147483647 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 8906 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:1437) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.140:10122;received=192.168.1.2;rport=1437;branch=z 9hG4bK-d87543-723677665-1--d875 43-
Record-Route: <sip:192.168.1.140>
From: mete <sip:001@192.168.1.140>;tag=1e57a20f
To: <sip:905322744114@192.168.1.80:5094>;tag=1077c6e
Call-ID: 141f573e2366530b123
CSeq: 1 INVITE
Contact: <sip:111@192.168.1.80:5094>
x-customheader-extension-111: "This is a modified transmitted SIP message."
x-phoneline: 0
Server: LanScape Centrex Proxy/3.42.2.6 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   175

v=0
o=LanScape 2147483647 2147483647 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 8906 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20

************* Log Closed (Oct 19 11:35:03) *************


Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights