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 - PSTN Gateway Timeout Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 05 2006 at 11:56am | IP Logged Quote juice
Hi,

I have installed Centrex Proxy Server and VOIP Media Proxy (Trial), both are running on same machine, I'm able to make internal calls between users.
I have configured Call Routing for PSTN gateway:

Username/Phone: 00[0-9]*
Routing Information: 63.214.186.150:5060
[X]Username/Phone is specified as regular expression
Optional dialing prefix: 00

the problem i'm facing is following, when i do place a call 0049123456789 the sip proxy and media proxy are reporting Call Start event, but after few second client receives Request Timeout message.

on PSTN Gateway I have run tcpdump and asterisk in sip debug mode and there is no signaling coming, see attached Sip Log.

-----BEGIN LOG

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 82.83.88.222:35558) <<<<
INVITE sip:0049123456789@63.214.186.148 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.101:35558;branch=z9hG4bK-d87543-0e3bf4016636a423-1 --d87543-;rport
Max-Forwards: 70
Contact: <sip:user@82.83.88.222:35558>
To: "0049123456789"<sip:0049123456789@63.214.186.148>
From: "user"<sip:user@63.214.186.148>;tag=86223829
Call-ID: MWU2NTVhZmRiNDU1NDhiMDg3OWE4YjE1YTE0Zjk3ZDc.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 377

v=0
o=- 5 2 IN IP4 192.168.1.101
s=CounterPath X-Lite 3.0
c=IN IP4 192.168.1.101
t=0 0
m=audio 48346 RTP/AVP 107 119 0 98 8 3 101
a=alt:1 2 : q9IirobT BmIrjjNs 169.254.2.2 48346
a=alt:2 1 : abxHB/TT W/0g2QgH 192.168.1.101 48346
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


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 82.83.88.222:35558) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.101:35558;branch=z9hG4bK-d87543-0e3bf4016636a423-1 --d87543-;rport=35558;received=82.83.88.222
From: "user" <sip:user@63.214.186.148>;tag=86223829
To: "0049123456789" <sip:0049123456789@63.214.186.148>
Call-ID: MWU2NTVhZmRiNDU1NDhiMDg3OWE4YjE1YTE0Zjk3ZDc.
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.0.0 (www.LanScapeCorp.com)
Content-Length: 0



>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 63.214.186.148:0) >>>>
INVITE sip:63.214.186.150%3A5060@:0 SIP/2.0
Via: SIP/2.0/UDP 63.214.186.148:5060;branch=z9hG4bKffed890521ed9f1fb7d4884bb9 42fd0f2.0
Via: SIP/2.0/UDP 192.168.1.101:35558;branch=z9hG4bK-d87543-0e3bf4016636a423-1 --d87543-;rport=35558;received=82.83.88.222
Record-Route: <sip:63.214.186.148:5060;lr>
From: "user" <sip:user@63.214.186.148>;tag=86223829
To: "0049123456789" <sip:49123456789@:0>
Call-ID: MWU2NTVhZmRiNDU1NDhiMDg3OWE4YjE1YTE0Zjk3ZDc.
CSeq: 1 INVITE
Contact: <sip:user@8.128.87.0:35558>
max-forwards: 69
x-Rtp-Synch: Src
Server: LanScape Centrex Proxy/3.42.0.0 (www.LanScapeCorp.com)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Content-Length:   379

v=0
o=- 5 2 IN IP4 63.214.186.148
s=CounterPath X-Lite 3.0
c=IN IP4 63.214.186.148
t=0 0
m=audio 16001 RTP/AVP 107 119 0 98 8 3 101
a=alt:1 2 : q9IirobT BmIrjjNs 169.254.2.2 48346
a=alt:2 1 : abxHB/TT W/0g2QgH 192.168.1.101 48346
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


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 63.214.186.148:0) >>>>
INVITE sip:63.214.186.150%3A5060@:0 SIP/2.0
Via: SIP/2.0/UDP 63.214.186.148:5060;branch=z9hG4bKffed890521ed9f1fb7d4884bb9 42fd0f2.0
Via: SIP/2.0/UDP 192.168.1.101:35558;branch=z9hG4bK-d87543-0e3bf4016636a423-1 --d87543-;rport=35558;received=82.83.88.222
Record-Route: <sip:63.214.186.148:5060;lr>
From: "user" <sip:user@63.214.186.148>;tag=86223829
To: "0049123456789" <sip:49123456789@:0>
Call-ID: MWU2NTVhZmRiNDU1NDhiMDg3OWE4YjE1YTE0Zjk3ZDc.
CSeq: 1 INVITE
Contact: <sip:user@8.128.87.0:35558>
max-forwards: 69
x-Rtp-Synch: Src
Server: LanScape Centrex Proxy/3.42.0.0 (www.LanScapeCorp.com)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Content-Length:   379

v=0
o=- 5 2 IN IP4 63.214.186.148
s=CounterPath X-Lite 3.0
c=IN IP4 63.214.186.148
t=0 0
m=audio 16001 RTP/AVP 107 119 0 98 8 3 101
a=alt:1 2 : q9IirobT BmIrjjNs 169.254.2.2 48346
a=alt:2 1 : abxHB/TT W/0g2QgH 192.168.1.101 48346
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


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 63.214.186.148:0) >>>>
INVITE sip:63.214.186.150%3A5060@:0 SIP/2.0
Via: SIP/2.0/UDP 63.214.186.148:5060;branch=z9hG4bKffed890521ed9f1fb7d4884bb9 42fd0f2.0
Via: SIP/2.0/UDP 192.168.1.101:35558;branch=z9hG4bK-d87543-0e3bf4016636a423-1 --


-----END LOG


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: December 05 2006 at 12:44pm | IP Logged Quote support
Hi Andrew,

Ahhh.... We can see that the outgoing INVITE request line is hosed. We will look right into it.

Good job with your explanation and the fact that you have posted a SIP log file from the Centrex proxy. That’s exactly the information we need.

Hold tight as we look into this....

Support
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: December 05 2006 at 1:10pm | IP Logged Quote support
Hi Andrew,

We see it here too. We need the version of your CentrexProxy.exe image.

Right click on the CentrexProxy.exe image and select Properties. Goto the Version tab. We need the value of the "File version" string.

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


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 05 2006 at 1:24pm | IP Logged Quote juice
List of files and versions i have used for setup:

Trial LanScape Centrex Proxy Server Enterprise Setup.exe 3.42.0.0
Trial LanScape Service Manager Setup.exe 2.0.5.3
Trial LanScape VOIP Media Proxy Server Enterprise Setup.exe 2.72.0.0

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: December 05 2006 at 2:29pm | IP Logged Quote support
Hi Andrew,

Thanks for waiting. It looks as though we located the culprit. We just recently released the 3.42.0.0 Centrex proxy. It seems that we left in the retail product a piece of conditionally compiled test code that should have not been there. I don’t think we’ve ever done that one before.

I will send you and FTP login so you can download an updated Centrex proxy EXE binary image.

In the meantime, we will take another look at our 3.42.0.0 release one more time to make sure nothing else is hosed. Ya gotta like software…


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


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 05 2006 at 4:24pm | IP Logged Quote juice
Works like a charm :-)

I have another small issue related to Call Routing, I wanted to create route like this:

Username/Phone: [0-9]*
Routing Information: 63.214.186.150:5060
[X]Username/Phone is specified as regular expression
Optional dialing prefix:

So if called username/phone contains only numbers - route to PSTN gateway. Unfortunately it does not work and raises Not Found error however when i try [Test Regular Expression] it Match and shows Result correctly, so I was kind of forced to use this route:

Username/Phone: 00[0-9]*
Routing Information: 63.214.186.150:5060
[X]Username/Phone is specified as regular expression
Optional dialing prefix: 00

Am I missing something?

Andrew
Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 05 2006 at 4:39pm | IP Logged Quote juice
Small update to last post, i was trying to use

Username/Phone: [0-9]+
not Username/Phone: [0-9]* as above

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: December 05 2006 at 5:37pm | IP Logged Quote support
Hi Andrew,

We will have to look into that one. As theory goes, if the regular expression matches using the call routing config page (using the "Test" button on the "Add Call Routing Information" dialog), then in real-time, any call destination containing only numerics should route to the regular expression destination - the PSTN gateway.

We will give it a look in the morning. The support group is closing an hour earlier today. It’s the CTO's birthday.

Good questions. Repost as needed,

Support
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: December 05 2006 at 5:38pm | IP Logged Quote support
... for any more questions, feel free to start a new thread. This thread is getting a bit long.

Support
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: December 06 2006 at 8:40am | IP Logged Quote support
Hi Andrew,

We tested a call routing regular expression of [0-9]+ and it works OK. Here is what we did:

Goto the proxy server settings - call routing dialog.
We specified settings to route all call destinations containing only numbers but starting with a dialing prefix of 00 to a test gateway here in our lab.

These are the settings we used:

User name/phone number: [0-9]+
Routing information: 192.168.1.80:5060
User name/phone number as regular expression: Checked
Optional dialing prefix: 00

Performed a test in the dialog using the call destination 00123456. Pressed the "Test" button. The regular expression matched and the final call number was "123456".

Note: we also did a test specifying "Routing information" using a host name like: "\\TestGateway:5060" and that worked too.

Here is a sip proxy log:

Code:

************* Log Opened (Dec 06 08:38:50) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:00123456@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK007142e7
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:00123456@ps>
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
Max-Forwards: 70
Organization: 29645FED-6FAC-4688-91BD-05CAF8F13073
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 7418843 7418843 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 36528 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=z9hG4bK007142e7;received= 192.168.1.2
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:00123456@ps>
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
INVITE sip:123456@192.168.1.80:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKfc1c27c33fa1c82068d0893247771 b3bc.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK007142e7;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80:5060>
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
max-forwards: 69
organization: 29645FED-6FAC-4688-91BD-05CAF8F13073
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   221

v=0
o=333 7418843 7418843 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16001 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:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKfc1c27c3 3fa1c82068d0893247771b3bc.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK007142e7
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80:5060>
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Content-Length: 0






<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKfc1c27c3 3fa1c82068d0893247771b3bc.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK007142e7
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80:5060>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.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 4bK007142e7
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80:5060>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKfc1c27c3 3fa1c82068d0893247771b3bc.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK007142e7
Record-Route: <sip:192.168.1.2>
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-Id: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
Contact: <sip:1111@192.168.1.80:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Content-Length: 176
Content-Type: application/sdp

v=0
o=LanScape 3374404616 3374404616 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 16102 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 4bK007142e7
Record-Route: <sip:192.168.1.2>
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 INVITE
Contact: <sip:1111@192.168.1.80:5060>
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   174

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




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:00123456@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK007142e7
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-Id: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:1111@192.168.1.80>
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
ACK sip:1111@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKlc1c27c33fa1c82068d0893247771 b3bc
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK007142e7
Route: <sip:1111@192.168.1.80>
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434430 ACK
max-forwards: 69
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
BYE sip:1111@192.168.1.80 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK00719881
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-Id: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434431 BYE
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:1111@192.168.1.80>
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
BYE sip:1111@192.168.1.80 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf57e16e9a23e1a50176ad6a8ad659 13fd.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK00719881;received= 192.168.1.2
Route: <sip:1111@192.168.1.80>
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434431 BYE
max-forwards: 69
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf57e16e9 a23e1a50176ad6a8ad65913fd.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00719881
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-Id: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434431 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
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 4bK00719881
From: "Extension 333" <sip:333@ps>;tag=719589;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:123456@192.168.1.80>;tag=7a933a3
Call-ID: 07850094-b49d-410b-80bb-f84b28733809-0000076c@192.168.1.2
CSeq: 7434431 BYE
Server: LanScape Centrex Proxy/3.42.0.1 (www.LanScapeCorp.com)
Content-Length: 0

************* Log Closed (Dec 06 08:39:46) *************



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


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 06 2006 at 10:27am | IP Logged Quote juice
What I mean is, I want to dial "18580001111" and want it to be routed unchanged to PSTN gateway "18580001111", there is no prefix, so I've tried this settings:

Username/Phone: [0-9]+
Routing Information: 63.214.186.150:5060
[X]Username/Phone is specified as regular expression
Optional dialing prefix:

Where "Optional dialing prefix" is empty, there's no prefix to remove, all numeric as is should be routed to PSTN gateway. In this case it does not work.

This is not so important, only wanted to use dial plan based on CountryCode + Area Code + Number

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: December 06 2006 at 11:23am | IP Logged Quote support
Andrew,

Oooooh... now I understand what you mean. We will look at it again.

Support
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: December 06 2006 at 12:36pm | IP Logged Quote support
Hi Andrew,

We looked back into what you were talking about and found an interesting item.

When a call is being processed, the proxy always wants to use "prefix digits" and strip them off. I looked back into our records and sure enough, the regular expression routing was originally developed to always be used when prefix dialing digits are defined.

This is a limitation that does not have to exist. We have removed this limitation and ran your stated test again. Now the call is routed as expected.

Below is the SIP log from the latest test.

Note: You might want to use the ^[0-9]+$ regular expression string to match call destinations that are only all numbers. The [0-9]+ can match things like:

asw18580001111
zz18580001111

which may not be what you want.

There is a new proxy EXE image in your FTP support account. Grab it if you want.



Code:

************* Log Opened (Dec 06 12:37:24) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:18580001111@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK005b9cad
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@ps>
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
Max-Forwards: 70
Organization: 29645FED-6FAC-4688-91BD-05CAF8F13073
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 5980578 5980578 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 39412 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=z9hG4bK005b9cad;received= 192.168.1.2
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@ps>
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
INVITE sip:18580001111@192.168.1.80:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf68b22c5f252238b592f54faa5aab bfe8.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK005b9cad;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80:5060>
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
max-forwards: 69
organization: 29645FED-6FAC-4688-91BD-05CAF8F13073
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   221

v=0
o=333 5980578 5980578 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16001 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:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf68b22c5 f252238b592f54faa5aabbfe8.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005b9cad
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80:5060>
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Content-Length: 0






<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf68b22c5 f252238b592f54faa5aabbfe8.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005b9cad
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80:5060>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.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 4bK005b9cad
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80:5060>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKf68b22c5 f252238b592f54faa5aabbfe8.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005b9cad
Record-Route: <sip:192.168.1.2>
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-Id: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
Contact: <sip:1111@192.168.1.80:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
Content-Length: 176
Content-Type: application/sdp

v=0
o=LanScape 3374418884 3374418884 IN IP4 192.168.1.80
s=LanScape
c=IN IP4 192.168.1.80
t=0 0
m=audio 16116 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 4bK005b9cad
Record-Route: <sip:192.168.1.2>
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 INVITE
Contact: <sip:1111@192.168.1.80:5060>
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   174

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




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:18580001111@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005b9cad
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-Id: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:1111@192.168.1.80>
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
ACK sip:1111@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKl68b22c5f252238b592f54faa5aab bfe8
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005b9cad
Route: <sip:1111@192.168.1.80>
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003780 ACK
max-forwards: 69
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
BYE sip:1111@192.168.1.80 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK005baf6d
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-Id: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003781 BYE
Max-Forwards: 70
Route: <sip:192.168.1.2>,<sip:1111@192.168.1.80>
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.80:5060) >>>>
BYE sip:1111@192.168.1.80 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKfc9e5bdaaf52b1f8f550343be3869 bceb.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK005baf6d;received= 192.168.1.2
Route: <sip:1111@192.168.1.80>
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003781 BYE
max-forwards: 69
x-mycustomheader: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.80:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;branch=z9hG4bKfc9e5bda af52b1f8f550343be3869bceb.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK005baf6d
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-Id: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003781 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.8 (www.LanScapeCorp.com)
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 4bK005baf6d
From: "Extension 333" <sip:333@ps>;tag=5b86ff;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:18580001111@192.168.1.80>;tag=882ec6d
Call-ID: d490eaa5-97dd-47df-80dd-3c126350905e-00001edc@192.168.1.2
CSeq: 6003781 BYE
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0


************* Log Closed (Dec 06 12:37:45) *************


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


Joined: December 05 2006
Location: United States
Posts: 139
Posted: December 06 2006 at 2:59pm | IP Logged Quote juice
Works perfect, I did not use ^[0-9]+$ becouse I was suggested reading your help file were is example 9[0-9]* to not use the "^" beginning and "$" end of string symbols as it's auto included :-) , thanks for hint.

Andrew
Back to Top View juice's Profile Search for other posts by juice
 

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