Are you sure calls were dropped with change in IP ?? I think it should let current calls run and use new IP for new connections . However if destination serv drops calls then it's a different story .
On 03/07/07, Henry J. Cobb <[EMAIL PROTECTED]> wrote:
Asterisk 1.4.5 full log: [Jul 2 09:31:16] VERBOSE[2682] logger.c: == Refreshing DNS lookups. [Jul 2 09:31:16] NOTICE[2682] dnsmgr.c: host 'outbound1.vitelity.net' changed from 64.2.142.17 to 64.2.142.29 [Jul 2 09:31:23] DEBUG[2711] jitterbuf.c: Attempting to exceed Jitterbuf max 600 timeslots And the calls are dropped. I fixed this by turning off enable in dnsmgr.conf My question is: Do you attempt to move existing IAX connections when you see a DNS change or do you leave the existing connections the fnord alone on their current IP addresses and simply use the DNS change for new connections? -HJC _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
