Hello,
if you are looking at sharing the same destination addresses, many
kamailio can connect to the same database.
If you have active-active LBs want to notify the other LB about a change
in a state of a destination, then you can use the event_route blocks
executed by dispatcher module to notif
.tr...@pocos.nl
> To: sr-users@lists.sip-router.org
> Date: Tue, 14 Jul 2015 13:53:25 +0200
> Subject: Re: [SR-Users] Kamailio Load balancing Across Multiple Asterisk
> Servers -Chanspy
>
> On Tuesday 14 July 2015 11:29:34 Jonathan Hunter wrote:
> > No such extension/contex
On Tuesday 14 July 2015 11:29:34 Jonathan Hunter wrote:
> No such extension/context *1022-MAGNORTH13@from-outside while calling
> Local channel[2015-07-14 10:49:38] NOTICE[15318]: app_dial.c:1003
> do_forward: Forwarding failed to dial
> 'Local/*1022-MAGNORTH13@from-outside'
This sounds l
and it allowed
connection, I will try that.
I will also consider your other option.
Many thanks for the prompt response.
Jon
> From: d.tr...@pocos.nl
> To: sr-users@lists.sip-router.org
> Date: Tue, 14 Jul 2015 13:19:48 +0200
> Subject: Re: [SR-Users] Kamailio Load balancing Across Multip
On Tuesday 14 July 2015 11:04:59 Jonathan Hunter wrote:
> The problem I have is when I send an INVITE from Asterisk Server, and then
> kamailio sends an INVITE back to the same Asterisk Server I get the
> following failure in asterisk console;
Is it just a warning or does the chanspy fail?
You
Hello Eric,
You need to multihome Kamailio so that it is simultaneously present on
the external and internal interfaces:
listen=udp:external.ip:5060
listen=udp:internal.ip:5060
Then, you need to force requests forwarded to the Asterisk boxes to go
out the internal interface explicitly.
As written many time in this mailing list it depends on what services
you want to provide using such "voice servers". If they are transparent
media relays then rtpproxy or mediaproxy(-ng) can help. Also you can
integrate it with your billing to authorize calls and limit their duration.
Though
