On Sat, Oct 22, 2011 at 6:10 PM, David Villasmil <david.villasmil.work@gmail.com> wrote:

Hello,

Thanks for your answer...

But then that's the same as killing it and reloading it, no?

David

On Sat, Oct 22, 2011 at 6:03 PM, Hynek Cihlar <hynek.cihlar@gmail.com> wrote:

I was also having issues with changing gateways. A solution I came up with was to have globally unique names and changing a gateway was actually destroying the old one and recreating a new one under new name. The downside is that DB lookup must be performed before new call is initiated.

Hynek

On Sat, Oct 22, 2011 at 5:15 PM, David Villasmil <david.villasmil.work@gmail.com> wrote:

Hello,

I understand that if I make a change in a gateway, like IP address I need to first kill the gw because fs doesn't updated the config until all sessions are finished.

If the gateway has no traffic, that's fine. But the idea would be for the change to take effect starting with the new incoming calls and allow the old ones to end normally.

Also, when you kill a gw and then reload it, and incoming call between the kill and the reload will NOT be handled... this is just not right for a production environment..

Is there any other way of doing this WITHOUT actually:

- not handling new incoming calls?

- having to kill the gw?

Thanks!

David

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org