[Serusers] X-Lite behind NAT + SER

Timur Elzhov elzhov at warelex.com
Tue Mar 29 19:23:03 CEST 2005


Hello guys.

I have X-Lite client on WinXP, which in installed on the Virtual
Machine (VM), which in turn is installed under Linux host on the
public host nf034.jinr.ru (IP 159.93.29.34). For sharing single network
card between Linux host and Windows guest systems, VM uses the NAT
technology.

At first I run SER on Linux at nf034.jinr.ru:5060 and point them as a
proxy for X-Lite in its configuration menu.

I successfully logged X-Lite to the SER proxy server, and then looked
at the X-Lite diagnostic (URI to which X-Lite is assigned is
sip:test at nf034.jinr.ru):


====================== -- cut -- ======================
X-Lite release 1103m build stamp 14262
License key: 334EB1FDABF14B00BD22E1C2442210A4

Established SIP protocol listen on: 172.16.218.128:5060

Discovered Port Restricted Single Mapped Port Symmetric NAT Firewall

SIP: 172.16.218.128:5060
RTP: 172.16.218.128:8000
NAT: 159.93.29.34

Discovering external SIP port on symmetric firewall...
PROXY#0: 159.93.29.34:5060


SEND TIME: 29675015
SEND >> 159.93.29.34:5060
REGISTER sip:nf034.jinr.ru SIP/2.0
Via: SIP/2.0/UDP 159.93.29.34:5060;rport;branch=z9hG4bK2E70AA83DC6248CF85502BCD5E251FC7
From: Test User <sip:test at nf034.jinr.ru>;tag=1898047871
To: Test User <sip:test at nf034.jinr.ru>
Contact: "Test User" <sip:test at 159.93.29.34:5060>
Call-ID: 3DE2CFB300024F7085AEB4169AF1E048 at nf034.jinr.ru
CSeq: 48982 REGISTER
Expires: 1800
Max-Forwards: 70
User-Agent: X-Lite release 1103m
Content-Length: 0
====================== -- cut -- ======================

So, glance at the Contact field gives that X-Lite maps
172.16.218.128:5060 to the public IP 159.93.29.34 but with the *same*
port 5060! The same we can see at the SER 'location' table in
mysql/ser table:

+----------+----------------------------+
| username | contact                    |
+----------+----------------------------+
| test     | sip:test at 159.93.29.34:5060 |
+----------+----------------------------+

But, I have SER running exactly at the 159.93.29.34:5060 that leads to
the ports conflict. How can I resolve this situation?

Thank you!


-- 
Best regards,
Timur V. Elzhov
COO
Warelex LLC




More information about the sr-users mailing list