When the stack is sending a message, unless the UA has told it what interface to send from, it consults the routing table to figure out what interface it should send on. If you have multiple interfaces, and either one will work, you are not guaranteed to get the one you are bound to (if you are not bound to both). So, the routing table has told us to send from an interface we are not bound to, and there isn't much we can do at this point.
As for why you are getting this behavior with REGISTER but not INVITE, I am not sure. Check the logs and make sure it is trying to send to exactly the same place in both cases. It is also possible that DUM is specifying the local interface explicitly for INVITE, but not REGISTER (I do not know why this might be happening, but I am not terribly familiar with DUM).
Best regards, Byron Campen
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 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.
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 _______________________________________________ resiprocate-devel mailing list
|