Hi All,
I am using kamailio as dispatcher and set up kamailio just to send 200 okay back for the method register, I would like check if its normal for the kamailio send another invite on the next proxy listed on my dispatcher.lst after the first proxy process the invite and auth. Below is how the call is being process.
user kamailio 1proxy 2proxy user2 invite |----------> | 100 | <---------- | invite | | ---------> | 100 |<--------- | auth |<-----------| auth | <------------------------| ack |------------->| ---------->| Invite |-------------->| --------------------------> | then process
Is there any I can limit this? or it is realy the behavior?
Thanks a lot! Maurice
Hello,
seems you use round robin algorithm. You can use hash over call id if you want that same path is preserved for same Call-ID value.
If you want to use round robin, you have to use htable to store where the INVITE was sent first time, and when it comes second time with auth credentials, use the address from htable instead of dispatcher.
Cheers, Daniel
On 11/5/12 7:02 AM, Maurice Vistan wrote:
Hi All, I am using kamailio as dispatcher and set up kamailio just to send 200 okay back for the method register, I would like check if its normal for the kamailio send another invite on the next proxy listed on my dispatcher.lst after the first proxy process the invite and auth. Below is how the call is being process. user kamailio 1proxy 2proxy user2 invite |----------> | 100 | <---------- | invite | | ---------> | 100 |<--------- | auth |<-----------| auth | <------------------------| ack |------------->| ---------->| Invite |-------------->| --------------------------> | then process Is there any I can limit this? or it is realy the behavior? Thanks a lot! Maurice
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Daniel,
Thanks for the reply, Ill will study the htable and let you know what happens.
thanks! Maurice
On Mon, Nov 5, 2012 at 6:06 PM, Daniel-Constantin Mierla miconda@gmail.comwrote:
Hello,
seems you use round robin algorithm. You can use hash over call id if you want that same path is preserved for same Call-ID value.
If you want to use round robin, you have to use htable to store where the INVITE was sent first time, and when it comes second time with auth credentials, use the address from htable instead of dispatcher.
Cheers, Daniel
On 11/5/12 7:02 AM, Maurice Vistan wrote:
Hi All,
I am using kamailio as dispatcher and set up kamailio just to send 200 okay back for the method register, I would like check if its normal for the kamailio send another invite on the next proxy listed on my dispatcher.lst after the first proxy process the invite and auth. Below is how the call is being process.
user kamailio 1proxy 2proxy user2invite |----------> | 100 | <---------- | invite | | ---------> | 100 |<--------- | auth |<-----------| auth | <------------------------| ack |------------->| ---------->| Invite |-------------->| --------------------------> | then process
Is there any I can limit this? or it is realy the behavior?
Thanks a lot! Maurice
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
-
Daniel-Constantin Mierla -
Maurice Vistan