Hello List. I have a question about how SIP and SER work with the Registered Endpoints. Suppose that i have and endpoint with obtaining IP by DHCP. In the first attemp the REGISTER have the IP : 10.0.0.1. Suppose that after a while the enpoint is disconnected and connected again, so by DHCP it takes another IP, for example 10.0.0.5. So in my location table i see. ----- aor : '5555832351' Contact : 'sip:5555832351@10.0.0.1' Expires : 642 ----- aor : '5555832351' Contact : 'sip:5555832351@10.0.0.5' Expires : 3000 ----
So when i call to the 555-5832351 SER generates two INVITES (to the 2 registered endpoints) but only the 10.0.0.5 answer the call. So far this is not a problem, but suppose now that a new endpoint with number 5555832359 obtain by DHCP the old IP 10.0.0.1, so it tries to register with the SIP-Proxy . What i see in the location table is now:
----- aor : '5555832359' Contact : 'sip:5555832359@10.0.0.1' Expires : 3000 ----- aor : '5555832351' Contact : 'sip:5555832351@10.0.0.1' Expires : 442 ----- aor : '5555832351' Contact : 'sip:5555832351@10.0.0.5' Expires : 2800 ----
So when i call to the 555-5832351 the INVITE goes to these 3 endpoints. Generating too much traffic and erroneus RESPONSE messages in SER and in the endpoints. My question is : Is posible only permit one IP address per endpoint registered in the location table?. Or make sure that only one endpoint with a given IP and URI is registered in the location DB?.
Thanks in advance Best Regards
Ricardo.-
Hi Ricardo,
I see your problem. What you can do is to set registrar module to use only the most recent registered contact: modparam("registrar","append_branches", 0) modparam("registrar","desc_time_order", 1)
Other thing you can do is to limit the registration time modparam("registrar","max_expires", 300)
to use this, be sure your SIP clients supports expire modification by server.
Best regards, Marian Dumitru
Ricardo Martinez wrote:
Hello List. I have a question about how SIP and SER work with the Registered Endpoints. Suppose that i have and endpoint with obtaining IP by DHCP. In the first attemp the REGISTER have the IP : 10.0.0.1. Suppose that after a while the enpoint is disconnected and connected again, so by DHCP it takes another IP, for example 10.0.0.5. So in my location table i see.
aor : '5555832351' Contact : 'sip:5555832351@10.0.0.1' Expires : 642
aor : '5555832351' Contact : 'sip:5555832351@10.0.0.5' Expires : 3000
So when i call to the 555-5832351 SER generates two INVITES (to the 2 registered endpoints) but only the 10.0.0.5 answer the call. So far this is not a problem, but suppose now that a new endpoint with number 5555832359 obtain by DHCP the old IP 10.0.0.1, so it tries to register with the SIP-Proxy . What i see in the location table is now:
aor : '5555832359' Contact : 'sip:5555832359@10.0.0.1' Expires : 3000
aor : '5555832351' Contact : 'sip:5555832351@10.0.0.1' Expires : 442
aor : '5555832351' Contact : 'sip:5555832351@10.0.0.5' Expires : 2800
So when i call to the 555-5832351 the INVITE goes to these 3 endpoints. Generating too much traffic and erroneus RESPONSE messages in SER and in the endpoints. My question is : Is posible only permit one IP address per endpoint registered in the location table?. Or make sure that only one endpoint with a given IP and URI is registered in the location DB?.
Thanks in advance Best Regards
Ricardo.-
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
On 27-10 19:07, Marian Dumitru wrote:
Hi Ricardo,
I see your problem. What you can do is to set registrar module to use only the most recent registered contact: modparam("registrar","append_branches", 0) modparam("registrar","desc_time_order", 1)
Other thing you can do is to limit the registration time modparam("registrar","max_expires", 300)
to use this, be sure your SIP clients supports expire modification by server.
Unfortunately this is mutually exclusive with nathelper. Nathelper will rewrite the IP in Contact with the source IP of the packet carrying the REGISTER message and user agents will not be able to match the Contact in 200 OK and thus update the expires value.
This has been fixed in the development version of ser. It does not rewrite the IP in Contact anymore, the source IP of the REGISTER message is stored separately in the user location database.
Jan.