Re: [reSIProcate-users] Does resiprocate reregister when network IP changes?
Adding (or removing) transports at runtime is not currently supported. If you are not using
INADDR_ANY (ie. 0.0.0.0) as the interface address, then you will need to completely restart the stack, when a new IP address is available.
Scott
On Wed, Mar 7, 2012 at 4:24 PM, Nauman Sulaiman
<nauman762-home@xxxxxxxxxxx> wrote:
If my app is specifying the interface to use with the addTransport method, do I simply just need to call
this method each time the network ip changes. I can't see a removeTransport anywhere. To support VPN
we may need to control this rather than bind the resip transports to INADDR_ANY.
Sent: Wednesday, 7 March 2012, 20:51
Subject: Re: [reSIProcate-users] Does resiprocate reregister when network IP changes?
You should be able to leave it as is.
Scott
On Wed, Mar 7, 2012 at 2:15 PM, Nauman Sulaiman
<nauman762-home@xxxxxxxxxxx> wrote:
Thanks Scott
Just one other thing if the network goes away (no interfaces at all), does one need to destroy the stack and recreate
it when the network is back up or can it be safely left as it is then reregister when a network interface is available again.
If you bind the resip transports to INADDR_ANY (ie. 0.0.0.0) then resip will let the OS decide which interface to use when routing a particular request. The selected interface ip address get's added to the Via and Contact headers by the stack. That being said, if the interface used during registration goes away, then the application will need to unregister the old Contact Address and re-Register (the stack will now use the new interface). Unless you are setting the OverrideHostAndPort profile settings you should be fine in just re-using
the same Profile object.