How do you make outgoing registrations to sip providers' accounts?
I haven't found Kamailio functionality like this, so looks this requires some b2bua usage?
Is there some other way?
On 1/13/10 11:22 AM, Andrey Utkin wrote:
How do you make outgoing registrations to sip providers' accounts?
I haven't found Kamailio functionality like this, so looks this requires some b2bua usage?
Is there some other way?
does not require b2bua and it is not that complex to implement (code for auth is there, just needs the structure to hold active registration states to refresh at expire time), I was even thinking to do it at some point, but the work to get 3.0.0 out kept me busy.
You can use sipsak (via crond) or maybe sems to register cotacts pointing to your sip server, e.g., username@yourporxyipandport, and then you simply route inbound calls as usually.
Cheers, Daniel
El Miércoles, 13 de Enero de 2010, Daniel-Constantin Mierla escribió:
On 1/13/10 11:22 AM, Andrey Utkin wrote:
How do you make outgoing registrations to sip providers' accounts?
I haven't found Kamailio functionality like this, so looks this requires some b2bua usage?
Is there some other way?
does not require b2bua and it is not that complex to implement (code for auth is there, just needs the structure to hold active registration states to refresh at expire time), I was even thinking to do it at some point, but the work to get 3.0.0 out kept me busy.
You can use sipsak (via crond) or maybe sems to register cotacts pointing to your sip server, e.g., username@yourporxyipandport, and then you simply route inbound calls as usually.
But also ensure that your Kamailio and sipsak are not behind NAT. If not, in case the provider performs NAT "fixing" it would send incoming calls to the source IP from which sipsak sends the REGISTER.
On 1/13/10 12:43 PM, Iñaki Baz Castillo wrote:
El Miércoles, 13 de Enero de 2010, Daniel-Constantin Mierla escribió:
On 1/13/10 11:22 AM, Andrey Utkin wrote:
How do you make outgoing registrations to sip providers' accounts?
I haven't found Kamailio functionality like this, so looks this requires some b2bua usage?
Is there some other way?
does not require b2bua and it is not that complex to implement (code for auth is there, just needs the structure to hold active registration states to refresh at expire time), I was even thinking to do it at some point, but the work to get 3.0.0 out kept me busy.
You can use sipsak (via crond) or maybe sems to register cotacts pointing to your sip server, e.g., username@yourporxyipandport, and then you simply route inbound calls as usually.
But also ensure that your Kamailio and sipsak are not behind NAT. If not, in case the provider performs NAT "fixing" it would send incoming calls to the source IP from which sipsak sends the REGISTER.
then sipsak should use kamailio as outbond proxy.
Cheers, Daniel
El Viernes, 15 de Enero de 2010, Daniel-Constantin Mierla escribió:
does not require b2bua and it is not that complex to implement (code for auth is there, just needs the structure to hold active registration states to refresh at expire time), I was even thinking to do it at some point, but the work to get 3.0.0 out kept me busy.
You can use sipsak (via crond) or maybe sems to register cotacts pointing to your sip server, e.g., username@yourporxyipandport, and then you simply route inbound calls as usually.
But also ensure that your Kamailio and sipsak are not behind NAT. If not, in case the provider performs NAT "fixing" it would send incoming calls to the source IP from which sipsak sends the REGISTER.
then sipsak should use kamailio as outbond proxy.
Or it could avoid using Kamailio as outbound proxy and set REGISTER "Contact" to the binding address of Kamailio :)
(but this wouldn't work if the provider ignores the "Contact" URI and instead takes the public source address:port :(
On 1/15/10 2:53 PM, Iñaki Baz Castillo wrote:
El Viernes, 15 de Enero de 2010, Daniel-Constantin Mierla escribió:
does not require b2bua and it is not that complex to implement (code for auth is there, just needs the structure to hold active registration states to refresh at expire time), I was even thinking to do it at some point, but the work to get 3.0.0 out kept me busy.
You can use sipsak (via crond) or maybe sems to register cotacts pointing to your sip server, e.g., username@yourporxyipandport, and then you simply route inbound calls as usually.
But also ensure that your Kamailio and sipsak are not behind NAT. If not, in case the provider performs NAT "fixing" it would send incoming calls to the source IP from which sipsak sends the REGISTER.
then sipsak should use kamailio as outbond proxy.
Or it could avoid using Kamailio as outbound proxy and set REGISTER "Contact" to the binding address of Kamailio :)
right :-) -- we should have a module in kamailio to reply that.
Cheers, Daniel
(but this wouldn't work if the provider ignores the "Contact" URI and instead takes the public source address:port :(
Hello,
On 1/13/10 11:22 AM, Andrey Utkin wrote:
How do you make outgoing registrations to sip providers' accounts?
I haven't found Kamailio functionality like this, so looks this requires some b2bua usage?
Is there some other way?
I just committed in master branch to the uac module this functionality.
you have to create uacreg table (see top of uac_reg.c file for now to get the sql) and fill the records. Then you have to set the reg_db_uri and reg_contact_addr in cfg: http://sip-router.org/docbook/sip-router/branch/master/modules_k/uac/uac.htm...
Populate then one record for each registration you want to do -- there are attributes for local user and remote user (l_ and r_). l_uuid must be unique across all registrations, being used to identify contact address in replies and incoming invites.
Testing and feedback is very appreciated. The module should run with kamailio_3.0 branch as well, just copy the module there.
Cheers, Daniel
-
Andrey Utkin -
Daniel-Constantin Mierla -
Iñaki Baz Castillo