[reSIProcate] Sip Register Binding Problem

Niraj Roy nroy at varaha.com
Tue Oct 24 09:30:14 CDT 2006


Hi,

          Is there any other way round to solve this problem?

          Because, in this case I can't re-use the port 5060 again with
other IP address.

          My doubts are.

          First why this occurs.?

          Secondly why especially with Registration not with the Invite one
.?

                   

Regards,

Niraj    

          

  _____  

From: Byron Campen [mailto:bcampen at estacado.net] 
Sent: Monday, October 23, 2006 7:24 PM
To: Niraj Roy
Cc: resiprocate-devel at list.sipfoundry.org
Subject: Re: [reSIProcate] Sip Register Binding Problem

 

            The only way to address this right now is to open up transports
on both IP addresses, or use INADDR_ANY. For a UA, this works relatively
well, but nat-traversal can become an issue.

 

Best regards,

Byron Campen





<image001.jpg>

 

Hi,

  

Using resiprocate I have found the following issues.

 

1.      My Linux machine has two NIC card. I have configured Ip of NIC-1
while adding transport using DUM. 

     While sending registration it chooses NIC-2 Ip address and hence gives
me 503 Service Unavailable.

      And any attempt to place INVITE call gets successfully done.

 

2.      I can see this same case happens when I am creating Virtual IP
address for a single NIC.

     It always selects an original IP though I have configured it for
Virtual one.

     Again while sending registration it sends same error as it comes in 1)
503 Service unavailable.

     And with INVITE it successfully run.

 

Any guess in this regards.?

 

Thanks,

Niraj

 

 

 

                   

 

 

<image001.jpg>

_______________________________________________

resiprocate-devel mailing list

resiprocate-devel at list.sipfoundry.org

https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061024/c5230796/attachment.htm>


More information about the resiprocate-devel mailing list