| Author |
|
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 13 2007 at 10:07am | IP Logged
|
|
|
We have PSTN Gateway which has two parts.
On IP Address 1 is MEDIA Gateway and on IP Address 2 is CALL CONTROL (SIP MESSAGING).
We have encountered some difficulties attempting to implement your products (SIP AND MEDIA PROXY).
Case scenario (which is required but we have not managed to make it works)
We have PSTN Gateway which contains two servers.
One with IP Address 1 acting as Media gateway and One with IP Address 2 acting as SIP CALL CONTROL.
The problem is that SIP messaging is working properly but Lanscape Media Proxy makes error when opening media session.
We believe that problem is in following facts.
Our CALL CONTROL (part of PSTN Gateway) which has IP Address 2 is sending IP Address 1 (which is IP Address of MEDIA GATEWAY, also part of PSTN Gateway) inside Connection information data in Session Description Protocol part of message.
Lanscape Proxy then receives this message and starts media session on media proxy but ignores that IP address (IP Address 1 media gateway server) and uses IP address of CALL CONTROL SERVER(IP Address 2) which has sent message.
The result is that call is officially established but there is no media flow.
Is it possible to make our case to work properly ?
With Regards,
A. Vedran
Logosoft d.o.o.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 13 2007 at 11:33am | IP Logged
|
|
|
Hi Vedran,
Nice posting and great graphic.
Can we make this scenario work? Yes. It sounds like it may be a simple software change.
To start, we will need a SIP log for a complete call set up that experiences media failure. We will also need to know IP addresses that are being used by SIP part and Media part of PSTN gateway and IP of the “Caller Phone”. Also the names and types of the VOIP devices as shown in your graphics (i.e. what PSTN gateway you are using and “caller phone” user agent, etc).
If you can enter into a support contract with us to help us cover the cost of making the software changes, this would be best. Also allowing our lab to have VPN access to your private network so that we may conduct full testing/verification would be required so that we may make the needed changes as fast as possible. Let us know what you want to do or what is possible at your end.
Thanks,
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 14 2007 at 4:25am | IP Logged
|
|
|
Hi,
Regarding support contract can you tell me what are costs of that.
We can supply information about network setup and provide you captured traffic (ethereal) but I'm not sure about VPN access.
One more question. Is it possible to make configuration changes to allow usage of stored procedures to manage user registration data ?
I'm waiting for answer.
With Regards,
A. Vedran
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 14 2007 at 7:49am | IP Logged
|
|
|
We made PDF DOCUMENT which presents our first problem in more details (with sip log,network diagram and some screen captures).
With Regards,
A. Vedran
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 15 2007 at 9:30am | IP Logged
|
|
|
Vedran,
Post a SIP log from the LanScape Centrex SIP proxy to this forum thread. We will review it.
We would hope that this will be a simple change. If so, then we will make the appropriate changes and get you updated product images to test.
If it is not simple, we will have to put this into a short support contract in order to modify the required code on the Centrex proxy and/or the media proxy. We can discuss further after you get us the SIP log.
Question:
Is this a single deployment or are you going to deploy many LanScape proxies?
You have done a great job in your problem description and graphic images. Thanks for that.
We will wait for you SIP log.
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 15 2007 at 9:36am | IP Logged
|
|
|
Hi,
There is log in document which can be downloaded from http://www.logosoft.ba/xxx/lanscapeSupport.pdf.
Do you need pure text files ?
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 15 2007 at 9:45am | IP Logged
|
|
|
I suggest that you look at http://www.logosoft.ba/xxx/lanscapeSupport.pdf because there is a log file with network diagrams and some screenshots of media and sip proxy messages.
Here is log content which causes error
Code:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 85.158.32.129:9455) <<<<
INVITE sip:0038514982011@lol.ba SIP/2.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:931023@85.158.32.129:9455;transport=udp>
To: <sip:0038514982011@lol.ba>
From: "Selmir Softic"<sip:931023@lol.ba>;tag=0f3b5769
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: Bria release 2.0 stamp 40829
Content-Length: 233
v=0
o=- 5 2 IN IP4 85.158.32.129
s=CounterPath CMC
c=IN IP4 85.158.32.129
t=0 0
m=audio 15796 RTP/AVP 0 8 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=x-rtp-session-id:76F3F8260FEC45A3B960BB0E390A4843
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 85.158.32.129:9455) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@lol.ba>
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
INVITE sip:0038514982011@217.75.205.5:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.62:5060;branch=z9hG4bKf2c314bf93331b558e5a6223d0c 74291e.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
Record-Route: <sip:217.75.205.62:5060;lr>
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Contact: <sip:931023@232.150.87.0:9455;transport=udp>
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Content-Length: 233
v=0
o=- 5 2 IN IP4 217.75.205.62
s=CounterPath CMC
c=IN IP4 217.75.205.62
t=0 0
m=audio 16001 RTP/AVP 0 8 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=x-rtp-session-id:76F3F8260FEC45A3B960BB0E390A4843
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.75.205.62:5060;branch=z9hG4bKf2c314bf93331b558e5a6223d0c 74291e.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.75.205.62:5060;branch=z9hG4bKf2c314bf93331b558e5a6223d0c 74291e.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Contact: <sip:0038514982011@217.75.205.5:5060>
Record-Route: <sip:217.75.205.62:5060;lr>
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 85.158.32.129:9455) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
Record-Route: <sip:217.75.205.62:5060;lr>
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Contact: <sip:0038514982011@217.75.205.5:5060>
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 217.75.205.62:5060;branch=z9hG4bKf2c314bf93331b558e5a6223d0c 74291e.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Contact: <sip:0038514982011@217.75.205.5:5060>
Record-Route: <sip:217.75.205.62:5060;lr>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDA TE
Supported: timer
Content-Type: application/sdp
Content-Length: 349
v=0
o=- 11517 0 IN IP4 217.75.205.35
s=Cisco SDP 0
c=IN IP4 217.75.205.35
t=0 0
m=audio 19050 RTP/AVP 0 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
!----------------------------------------------------
As you can see, information in above message about media session is pointing to rigth IP address and port of media gateway. This information is not properly interpreted by LanScape SIP/Media Proxy, please see Picture 2. (Port is OK, but IP address is wrong).
!-----------------------------------------------------
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 85.158.32.129:9455) >>>>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-446cdd7bdb241c1d-1- -d87543-;rport=9455;received=85.158.32.129
Record-Route: <sip:217.75.205.62:5060;lr>
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 INVITE
Contact: <sip:0038514982011@217.75.205.5:5060>
supported: timer
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Allow: INVITE, ACK, PRACK, SUBSCRIBE, BYE, CANCEL, NOTIFY, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length: 349
v=0
o=- 11517 0 IN IP4 217.75.205.62
s=Cisco SDP 0
c=IN IP4 217.75.205.62
t=0 0
m=audio 16001 RTP/AVP 0 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 85.158.32.129:9455) <<<<
ACK sip:0038514982011@217.75.205.5:5060 SIP/2.0
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-38556404ee12e058-1- -d87543-;rport
Max-Forwards: 70
Route: <sip:217.75.205.62:5060;lr>
Contact: <sip:931023@85.158.32.129:9455;transport=udp>
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
From: "Selmir Softic"<sip:931023@lol.ba>;tag=0f3b5769
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 ACK
User-Agent: Bria release 2.0 stamp 40829
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
ACK sip:0038514982011@217.75.205.5:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.62:5060;branch=z9hG4bKld57d8986a5102b31cbdcf0bcbc 491f9d
Via: SIP/2.0/UDP 85.158.32.129:9455;branch=z9hG4bK-d87543-38556404ee12e058-1- -d87543-;rport=9455
From: "Selmir Softic" <sip:931023@lol.ba>;tag=0f3b5769
To: <sip:0038514982011@217.75.205.5:5060>;tag=69197252
Call-ID: MDg3MGU0NmQ3ZTA0NDFhYzUzNjM3MjJiNGY5NDIyY2Y.
CSeq: 1 ACK
Contact: <sip:931023@85.158.32.129:9455;transport=udp>
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0
|
|
|
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 15 2007 at 2:05pm | IP Logged
|
|
|
Vedran
I like the way you do things :)
Very nice PDF file. Also showing the proxies GUIs is a good help also. You are superb.
We will look at the SIP log and your PDF info in depth.
Please answer these question:
Is this a single deployment or are you going to deploy many LanScape proxies?
How fast do you need a software update?
Thanks,
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 15 2007 at 3:07pm | IP Logged
|
|
|
Vedran,
For your LanScape SIP proxy, ZIP archive the entire install directory for the product trial and upload it to your support FTP account. We will send you the FTP details shortly.
We need your proxy's configuration info.
The default location shoule be something like:
"C:\Program Files LanScape\Centrex Proxy"
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 15 2007 at 3:18pm | IP Logged
|
|
|
Vedran,
Also, please create for us a backup INI file image of your SIP proxy setings. Go to the main menu and select:
Configure->Backup proxy configuration.
Specify an INI file and save the settings. Then please email that INI file to us at support.
Thanks,
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 15 2007 at 4:22pm | IP Logged
|
|
|
Sorry for delays
We are in Europe and right now here is 23:15 :)
We would like to have at least two SIP proxies at end to enable load balancing and failure safety. But we need to get things working very fast at least with one for start. As how fast we need update, well we are under pressure and if we do not solve this very fast we are going to be forced from our boss to search for alternative solution. I repeat that we like your product so that you dont get me wrong.
I need to contact my admin to access files so that he can send it back to you.
Will try to do that right now but it's very late.
Regards,
A. Vedran
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 15 2007 at 4:36pm | IP Logged
|
|
|
OK I'm sending configuration file to support mail.
I made zip of your products which we are testing (sip and media) and we are waiting for your ftp account to upload files.
Regards,
A. Vedran
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 15 2007 at 5:36pm | IP Logged
|
|
|
Upload completed.
Happy hunting
Regards,
A. Vedran
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 20 2007 at 11:52am | IP Logged
|
|
|
Hi Vedran,
Thanks for all the good information you have supplied to us. Based on your off line email conversations with our CTO, we have been able to quickly put together preliminary updated binary images of the Centrex Proxy Server and the VOIP Media Proxy Server for the “split media” deployment scenario you face.
You can download the updated trial binary images using your support FTP account. Please see in the “Image 1” directory of your FTP account.
There is a PDF document called “Engineering Notes.pdf” in your FTP account. It helps explain a bit about what the binary images are and what we will need from you after you perform your inter-op testing.
We will wait for your response. Please post your inter-op test results to this thread.
Thank you,
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 20 2007 at 12:38pm | IP Logged
|
|
|
Hi,
We have started first tests and so far looks good.
We will need some time to test multiple scenarios and after that we will submit results.
Regards,
A. Vedran
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 21 2007 at 3:51am | IP Logged
|
|
|
Hi,
Tests are showing some issues.
When we turn media proxy support on we have issues with strange behavior with forwarded INVITE requests.
The contact field IP address is changed to some random value with last byte always set to 0.
Result is that called side is unable to send valid BYE request.
Please look at contact values in received and forwarded INVITE.
Also look at the attempt of BYE request from Called party which will not terminate connections because of problem described above.
Regards,
A. Vedran
Code:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
INVITE sip:931021@217.75.205.72;user=phone SIP/2.0
Via: SIP/2.0/UDP 217.75.205.5:5060 ;branch=z9hG4bKterm-62-33931707-931021-74483
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Supported: timer
Session-Expires: 300
Min-SE: 10
Contact: <sip:33931707@217.75.205.5:5060>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDA TE
Max-Forwards: 10
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13232 0 IN IP4 217.75.205.35
s=Cisco SDP 0
c=IN IP4 217.75.205.35
t=0 0
m=audio 18048 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.50:5060) >>>>
INVITE sip:931021@217.75.205.50:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf73679f2718b13ba35f3df3932c 25b982.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:33931707@128.210.237.0:5060>
supported: timer
session-expires: 300
min-se: 10
max-forwards: 9
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Allow: INVITE, ACK, PRACK, SUBSCRIBE, BYE, CANCEL, NOTIFY, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13232 0 IN IP4 217.75.205.74
s=Cisco SDP 0
c=IN IP4 217.75.205.74
t=0 0
m=audio 16002 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf73679f2718b13ba35f3df3932c 25b982.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Server: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf73679f2718b13ba35f3df3932c 25b982.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Contact: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
Server: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Contact: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf73679f2718b13ba35f3df3932c 25b982.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Contact: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
Server: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Supported: replaces
Content-Length: 211
Content-Type: application/sdp
v=0
o=931021 6843071 6843071 IN IP4 217.75.205.50
s=Cisco 7905 SIP Call
c=IN IP4 217.75.205.50
t=0 0
m=audio 16384 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-7448 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 INVITE
Contact: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
supported: replaces
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Type: application/sdp
Content-Length: 211
v=0
o=931021 6843071 6843071 IN IP4 217.75.205.74
s=Cisco 7905 SIP Call
c=IN IP4 217.75.205.74
t=0 0
m=audio 16002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
ACK sip:217.75.205.72:5060;lr SIP/2.0
Via: SIP/2.0/UDP 217.75.205.5:5060 ;branch=z9hG4bKterm-62-33931707-931021-66454
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 ACK
Route: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.50:5060) >>>>
ACK sip:931021@217.75.205.72:5060;lr SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKl6aa086768edeb213081cc7421d e9b481
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-62-33931707-931021-6645 4;rport=5060
Route: cisco <sip:931021@217.75.205.50:5060;user=phone;transport=udp&g t;
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
To: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 ACK
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
BYE sip:33931707@128.210.237.0 SIP/2.0
Route: <sip:217.75.205.72:5060;lr>
Via: SIP/2.0/UDP 217.75.205.50:5060;branch=z9hG4bKf97efd174562e579
From: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 BYE
Max-Forwards: 70
User-Agent: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Supported: replaces, 100rel
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 128.210.237.0:5060) >>>>
BYE sip:33931707@128.210.237.0 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf83732dbfc299ebc427003229c3 355aa2.0
Via: SIP/2.0/UDP 217.75.205.50:5060;branch=z9hG4bKf97efd174562e579;rport=5060 ;received=217.75.205.50
From: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 BYE
max-forwards: 69
supported: replaces
supported: 100rel
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
BYE sip:33931707@128.210.237.0 SIP/2.0
Route: <sip:217.75.205.72:5060;lr>
Via: SIP/2.0/UDP 217.75.205.50:5060;branch=z9hG4bKf97efd174562e579
From: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 BYE
Max-Forwards: 70
User-Agent: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Supported: replaces, 100rel
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.50:5060) <<<<
BYE sip:33931707@128.210.237.0 SIP/2.0
Route: <sip:217.75.205.72:5060;lr>
Via: SIP/2.0/UDP 217.75.205.50:5060;branch=z9hG4bKf97efd174562e579
From: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 BYE
Max-Forwards: 70
User-Agent: Cisco-CP7905/8.0.1-060412A
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Supported: replaces, 100rel
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 128.210.237.0:5060) >>>>
BYE sip:33931707@128.210.237.0 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf83732dbfc299ebc427003229c3 355aa2.0
Via: SIP/2.0/UDP 217.75.205.50:5060;branch=z9hG4bKf97efd174562e579;rport=5060 ;received=217.75.205.50
From: 931021 <sip:931021@217.75.205.72;user=phone>;tag=2152219277
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=292382142
Call-ID: 61727226-2f56341c-5664cc2-38@217.75.205.5
CSeq: 1 BYE
max-forwards: 69
supported: replaces
supported: 100rel
Server: LanScape Centrex Proxy/3.42.1.10 (www.LanScapeCorp.com)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE
Content-Length: 0
|
|
|
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 21 2007 at 3:49pm | IP Logged
|
|
|
Vedran,
You can download an updated Centrex Proxy Server version from your support FTP account.
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 21 2007 at 6:34pm | IP Logged
|
|
|
Thank you.
We will test new software today.
Regards,
A. Vedran
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 22 2007 at 7:19am | IP Logged
|
|
|
Hi,
We have found another bug in SIP PROXY server.
When call is coming from non registered source the proxy changes contact IP address in invite request to local IP address of proxy server (217.75.205.72).
The IP address in contact must be the same as in original received INVITE otherwise there is no possibility to send proper bye request from called party.
Please look at received and forwarded INVITE requests in log.
Everything else seems to work properly.
With Regards,
A. Vedran
Code:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
INVITE sip:931012@217.75.205.72;user=phone SIP/2.0
Via: SIP/2.0/UDP 217.75.205.5:5060 ;branch=z9hG4bKterm-d9-33931707-931012-68706
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1621660356
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 3df31231-2ebc304c-5647ef0a-69@217.75.205.5
CSeq: 1 INVITE
Supported: timer
Session-Expires: 300
Min-SE: 10
Contact: <sip:33931707@217.75.205.5:5060>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDA TE
Max-Forwards: 10
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13941 0 IN IP4 217.75.205.35
s=Cisco SDP 0
c=IN IP4 217.75.205.35
t=0 0
m=audio 19094 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-d9-33931707-931012-6870 6;rport=5060;received=217.75.205.5
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1621660356
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 3df31231-2ebc304c-5647ef0a-69@217.75.205.5
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.59:5060) >>>>
INVITE sip:931012@217.75.205.59:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf6b4e969f53e83980aa57318601 373070.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-d9-33931707-931012-6870 6;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1621660356
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 3df31231-2ebc304c-5647ef0a-69@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:33931707@217.75.205.72:5060>
supported: timer
session-expires: 300
min-se: 10
max-forwards: 9
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Allow: INVITE, ACK, PRACK, SUBSCRIBE, BYE, CANCEL, NOTIFY, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13941 0 IN IP4 217.75.205.75
s=Cisco SDP 0
c=IN IP4 217.75.205.75
t=0 0
m=audio 16001 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
|
|
|
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 22 2007 at 7:45am | IP Logged
|
|
|
Vedran,
Can you post the entire SIP log showing call setup and BYE termination. We need to see the whole thing. the INVITE that is relayed to the call destination has "Record-Route:" header. This should make the destination User agent send its BYE to the LanScape SIP proxy no matter what. The LanScape SIP proxy will then forward the BYE appropriately to the Cisco SIP gateway.
Anyway, we need to see the whole log from the standpoint of the LanScape Centrex SIP proxy server.
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 22 2007 at 8:32am | IP Logged
|
|
|
Code:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
INVITE sip:931012@217.75.205.72;user=phone SIP/2.0
Via: SIP/2.0/UDP 217.75.205.5:5060 ;branch=z9hG4bKterm-da-33931707-931012-48093
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Supported: timer
Session-Expires: 300
Min-SE: 10
Contact: <sip:33931707@217.75.205.5:5060>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDA TE
Max-Forwards: 10
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13978 0 IN IP4 217.75.205.35
s=Cisco SDP 0
c=IN IP4 217.75.205.35
t=0 0
m=audio 18054 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.59:5060) >>>>
INVITE sip:931012@217.75.205.59:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf4170d5e06707d9866bdaba8a00 8f18a5.0
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:33931707@217.75.205.72:5060>
supported: timer
session-expires: 300
min-se: 10
max-forwards: 9
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Allow: INVITE, ACK, PRACK, SUBSCRIBE, BYE, CANCEL, NOTIFY, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length: 560
v=0
o=- 13978 0 IN IP4 217.75.205.75
s=Cisco SDP 0
c=IN IP4 217.75.205.75
t=0 0
m=audio 16001 RTP/AVP 0 8 99 101 2 102 4 103 104 105 106 18 0 125 100
a=rtpmap:99 G.726-16/8000
a=rtpmap:101 G.726-24/8000
a=rtpmap:102 G.723.1-H/8000
a=rtpmap:103 G.723.1-L/8000
a=rtpmap:104 G.729b/8000
a=rtpmap:105 G.723.1a-H/8000
a=rtpmap:106 G.723.1a-L/8000
a=rtpmap:125 G.nX64/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.59:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf4170d5e06707d9866bdaba8a00 8f18a5.0,SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:931012@217.75.205.59:5060;user=phone>
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:931012@217.75.205.59:5060;user=phone>
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.59:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKf4170d5e06707d9866bdaba8a00 8f18a5.0,SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:931012@217.75.205.59:5060;user=phone>
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,PRACK,REFER,NOTIFY
Supported: 100rel,replaces
Content-Type: application/sdp
Content-Length: 284
v=0
o=- 2599123659 2599123660 IN IP4 217.75.205.59
s=-
c=IN IP4 217.75.205.59
t=0 0
m=audio 50924 RTP/AVP 8
a=rtpmap:8 PCMA/8000/1
a=ptime:20
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.5:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-4809 3;rport=5060;received=217.75.205.5
Record-Route: <sip:217.75.205.72:5060;lr>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 INVITE
Contact: <sip:931012@217.75.205.59:5060;user=phone>
supported: 100rel
supported: replaces
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, UPDATE, PRACK, REFER, NOTIFY
Content-Type: application/sdp
Content-Length: 284
v=0
o=- 2599123659 2599123660 IN IP4 217.75.205.75
s=-
c=IN IP4 217.75.205.75
t=0 0
m=audio 16001 RTP/AVP 8
a=rtpmap:8 PCMA/8000/1
a=ptime:20
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.5:5060) <<<<
ACK sip:217.75.205.72:5060;lr SIP/2.0
Via: SIP/2.0/UDP 217.75.205.5:5060 ;branch=z9hG4bKterm-da-33931707-931012-87669
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 ACK
Route: <sip:931012@217.75.205.59:5060;user=phone>
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.59:5060) >>>>
ACK sip:931012@217.75.205.72:5060;lr SIP/2.0
Via: SIP/2.0/UDP 217.75.205.72:5060;branch=z9hG4bKl5058590db1936a0a5d1cdea03c 15405d
Via: SIP/2.0/UDP 217.75.205.5:5060;branch=z9hG4bKterm-da-33931707-931012-8766 9;rport=5060
Route: <sip:931012@217.75.205.59:5060;user=phone>
From: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
To: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 1 ACK
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 217.75.205.59:5060) <<<<
BYE sip:33931707@217.75.205.72:5060 SIP/2.0
Via: SIP/2.0/UDP 217.75.205.59:5060;branch=z9hG4bK2603733659-43464012
Route: <sip:217.75.205.72:5060;lr>
Max-Forwards: 70
From: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 2 BYE
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 217.75.205.59:5060) >>>>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 217.75.205.59:5060;branch=z9hG4bK2603733659-43464012;rport=5 060;received=217.75.205.59
From: 931012 <sip:931012@217.75.205.72;user=phone>;tag=KEYMILE_2599 118659-43464011
To: 33931707 <sip:33931707@217.75.205.5;user=phone>;tag=1651643070
Call-ID: 665a9387-3bc8523-14c8448-6a@217.75.205.5
CSeq: 2 BYE
Server: LanScape Centrex Proxy/3.42.1.11 (www.LanScapeCorp.com)
Content-Length: 0
|
|
|
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 22 2007 at 10:04am | IP Logged
|
|
|
Vedran,
So we completely understand the SIP log:
1)
Is the call coming from the PSTN gateway?
2)
Is the PSTN gateway registering with the LS SIP proxy?
(Probably not but we need to ask).
3)
Is the call destination (931012) registered with the LS proxy?
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 22 2007 at 10:41am | IP Logged
|
|
|
1 yes
2 no
3 yes
Regards,
A. Vedran
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 22 2007 at 11:12am | IP Logged
|
|
|
Vedran,
Yes, the contact header in the relayed INVITE should not be changed by the proxy and remain as:
Contact: <sip:33931707@217.75.205.5:5060>
This way the Route header in the received BYE message will tell the LS proxy where to forward the BYE.
An updated image is in directory "Image 3" of your support FTP account.
Support
|
| Back to Top |
|
| |
vedran
Intermediate
Joined: June 13 2007
Location: Bosnia Hercegovina
Posts: 18
|
| Posted: June 25 2007 at 7:54am | IP Logged
|
|
|
Hi,
We have completed initial tests with success. Now we will start beta phase which includes actual users of system. We would like to see are there going to be any unexpected behavior with system under real life usage.
Also we would like to know how to obtain our licenses for which we have agreed upon.
With Regards,
A. Vedran
|
| Back to Top |
|
| |
|
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> SIP Proxy and Media Proxy - Technical Support
Topic: Problem with different SIP / MEDIA IP addresses
