[Users] Openser not able to place calls to sipxezphone, no port mentioned in Contact URI

[Vamsi Pottangi]

Hi All,

Need help on resolving the incomign calls problems with sipxezphone which
openser as proxy

sizezphone sends "Contact:" URI as
sip:<usernamename>@<ipadd>;LINEID=<lineid>  rather than
sip:<username>@<ipadd>:<port>
For the same reason OpenSER is not able to route the incoming calls to
sipxezphone.

How can I make the sipxezphone(sipxtapi) to send Contact URI with port
number mentioned?

~~~Contact(0xb60deb38)~~~
domain    : 'location'
aor       : 'vamsi'
Contact   : 'sip:vamsi at 192.168.101.21;LINEID=a9bd64e174dc'
Expires   : 232
q         :
Call-ID   : '5dd7235bc92046fd79bb68788a7f5f55'
CSeq      : 1
User-Agent: 'sipXezPhone'
received  : ''
Path      : ''
State     : CS_SYNC
Flags     : 0
Sock      : 192.168.101.35:5060 (0x8145be8)
Methods   : 4294967295
next      : (nil)
prev      : (nil)
~~~/Contact~~~~



When I try to do NAT fixing on OpenSER, it records the port from which the
REGISTER message had recieved and tries to send the INVITE message to that
port, in this case  1617 rather than 5060. Actually sipzexphone is listening
on 1617 and 5060 as well which can be found from the below netsta -na output

When I snooped the messages, I found that sipzezphone is sending register
message using port 1617, though the DEFAULT_PORT is 5060

~~~Contact(0xb60deb38)~~~
domain    : 'location'
aor       : 'vamsi'
Contact   : 'sip:vamsi at 192.168.101.21;LINEID=a9bd64e174dc'
Expires   : 171
q         :
Call-ID   : 'e1102f18dca4dcb81363d75c605632fa'
CSeq      : 7
User-Agent: ''
received  : 'sip:192.168.101.21:1617'
Path      : ''
State     : CS_SYNC
Flags     : 0
Sock      : 192.168.101.35:5060 (0x8145be8)
Methods   : 4294967295
next      : (nil)
prev      : (nil)
~~~/Contact~~~~

C:\Documents and Settings\Administrator>netstat -na

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2701           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2702           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:42510          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:19989        0.0.0.0:0              LISTENING
  TCP    192.168.101.21:139     0.0.0.0:0              LISTENING
  TCP    192.168.101.21:1501    192.168.101.35:22      ESTABLISHED
  TCP    192.168.101.21:1554    192.168.101.21:1555    TIME_WAIT
  TCP    192.168.101.21:1615    192.168.101.21:1616    ESTABLISHED
  TCP    192.168.101.21:1616    192.168.101.21:1615    ESTABLISHED
  TCP    192.168.101.21:1621    192.168.101.35:5060    ESTABLISHED
  TCP    192.168.101.21:5060    0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1036           *:*
  UDP    0.0.0.0:1037           *:*
  UDP    0.0.0.0:1100           *:*
  UDP    0.0.0.0:1508           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:4573           *:*
  UDP    0.0.0.0:4588           *:*
  UDP    0.0.0.0:6060           *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1038         *:*
  UDP    127.0.0.1:1056         *:*
  UDP    127.0.0.1:1075         *:*
  UDP    127.0.0.1:1105         *:*
  UDP    192.168.101.21:123     *:*
  UDP    192.168.101.21:137     *:*
  UDP    192.168.101.21:138     *:*
  UDP    192.168.101.21:1617    *:*
  UDP    192.168.101.21:1618    *:*
  UDP    192.168.101.21:1619    *:*
  UDP    192.168.101.21:1620    *:*
  UDP    192.168.101.21:5060    *:*

C:\Documents and Settings\Administrator>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kamailio.org/pipermail/users/attachments/20060912/e46824c8/attachment.htm