On Oct 9, 2009, at 10:40 AM, Maciej Aniserowicz wrote:
Hello,
The issue is resolved. I feel stupid, because Michael Jerris was
right the first time. Setting external_rtp_ip and external_sip_ip to
$${local_ip_v4} made it work.
But the strange thing is: it SOMETIMES worked before without any
fig?
Thanks to both of you for your answers.
MA
- Original Message -
From: mercutioviz (via Nabble)
To: Maciej Aniserowicz
Sent: Thursday, October 08, 2009 7:06 PM
Subject: Re: [Freeswitch-users] gateway FS informs it's client FS about users
hanged up with a long d
On Thu, Oct 8, 2009 at 6:18 AM, Maciej Aniserowicz <
maciej.aniserow...@gmail.com> wrote:
>
> Both of the instances are run on the same machine, i just changed the
> default
> ports they use. Can anything else cause this strange behavior?
> MA
>
Did a packet capture yield any clues? That is, were
Both of the instances are run on the same machine, i just changed the default
ports they use. Can anything else cause this strange behavior?
MA
Michael Jerris wrote:
>
> Incorrect NAT configuration so one of the boxes is not actually
> getting a BYE.
>
>
> On Oct 5, 2009, at 3:13 AM, Macie
Incorrect NAT configuration so one of the boxes is not actually
getting a BYE.
On Oct 5, 2009, at 3:13 AM, Maciej Aniserowicz wrote:
Hi,
When I use two FreeSWITCH instances ('internal' and 'external'), all
users register to the 'external' instance which acts as a gateway by
'internal' in
