[SR-Users] Removing dispatcher entry

[Kamrul Khan]

hi,
thanks for your reply. so what you are saying is active calls will continue with the same server ? for example, lets say i have two entries in my dispatcher.
10.1.1.110.1.1.2
There are already 10 active calls between my Kamailio and 10.1.1.1 and i just removed 10.1.1.1 from dispatcher. So now if my Kamailio receives a BYE for any of the 10 active calls from upstream it will continue with 10.1.1.1 though its not in list. Right? Please correct me if I am wrong.

> Date: Sat, 11 Oct 2014 01:08:09 +0200
> From: carsten at ng-voice.com
> To: sr-users at lists.sip-router.org
> Subject: Re: [SR-Users] Removing dispatcher entry
> 
> Hi,
> 
> the dispatcher module does not care about active calls when you remove
> a destination. The calls and all related SIP-Signalling will simply
> continue. This is handled by SIP-Loose Routing, not by the dispatcher
> module. The dispatcher module manages only the initial decision, what
> Server to take.
> 
> Kind regards,
> Carsten
> 
> 
> 
> 2014-10-11 0:35 GMT+02:00 dodul <dodul at live.com>:
> > Hi,
> >
> > I have a small question. If I remove a server from my dispatcher while it
> > has existing calls, what's gonna happen to the next notifications or
> > requests of the live calls. Will it send them to the same server even though
> > the server is not listed on the dispatcher.  Or it will forward them to the
> > other servers listed in the dispatcher.
> >
> > Sent from my Samsung Galaxy smartphone.
> >
> >
> > -------- Original message --------
> > From: Corey Edwards <tensai at zmonkey.org>
> > Date:10-10-2014 10:28 (GMT-06:00)
> > To: "Kamailio (SER) - Users Mailing List" <sr-users at lists.sip-router.org>
> > Cc:
> > Subject: Re: [SR-Users] Problems configuring Kamailio on Centos 6.5
> >
> > On Thu, Oct 9, 2014 at 9:54 PM, logikanet <webmaster at logikanet.com> wrote:
> >
> > Good evening!
> >
> >  I've been trying to install Kamailio on a Centos 6.5 cloud , I'm able to
> > compile and install everything, if I run  : service kamailio start  it
> > starts kamailio and if I run  service kamailio status  I tells me that is
> > running on PID...  which is fine, however, if I tweak the
> > /usr/local/etc/kamailio/kamailio.conf  according to the instructions on
> > http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
> > , when I run service kamailio start It says "ok" , but when I run service
> > kamailio status I get " kamailio dead but subsys locked" , I copied and
> > pasted the settings on the web-site but they don't work, I also tried used
> > the original cfg file adding the "#!ifdef WITH_ASTERISK"  but It still
> > doesn't work, I'm not an expert on Kamailio I just want to use it as a
> > register server behind Asterisk , perhaps if you have a valid conf file that
> > I could use as a template for kamailio 4.0.1 this is what I have :
> >
> >
> > Kamailio is pretty good about printing out error logs when it fails to
> > start. The trick is to capture them. I would start by running Kamailio from
> > the command line in no-fork mode.
> >
> > # kamailio -DE
> >
> > Corey
> >
> >
> > _______________________________________________
> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> > sr-users at lists.sip-router.org
> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
> 
> 
> 
> -- 
> Carsten Bock
> CEO (Geschäftsführer)
> 
> ng-voice GmbH
> Schomburgstr. 80
> D-22767 Hamburg / Germany
> 
> http://www.ng-voice.com
> mailto:carsten at ng-voice.com
> 
> Office +49 40 5247593-0
> Fax +49 40 34927220
> 
> Sitz der Gesellschaft: Hamburg
> Registergericht: Amtsgericht Hamburg, HRB 120189
> Geschäftsführer: Carsten Bock
> Ust-ID: DE279344284
> 
> Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
> http://www.ng-voice.com/imprint/
> 
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20141011/21acf27a/attachment.html>