This does now...
/b
On Sep 10, 2009, at 4:52 AM, Jason White wrote:
>
> Yes, but by default the internal profile doesn't handle nat, which
> is why (if
> I recall correctly) it has been recommended that the external
> profile be used
> to register clients that are not on the local network wh
hi jason,
yes, we're aware of the external profile. but the sample profile shows only
how to register FS to SIP gateways - not external clients registering to FS.
the directory/default/*xml belongs to the internal profile. how can we
create another directory for external clients? we like to see sa
Nandy Dagondon wrote:
> for outside clients to register w/ the internal profile, the router has to
> forward port 5060 to FS. am i correct?
Yes, but by default the internal profile doesn't handle nat, which is why (if
I recall correctly) it has been recommended that the external profile be used
t
hi brian,
for outside clients to register w/ the internal profile, the router has to
forward port 5060 to FS. am i correct?
/nandy
On Wed, Sep 9, 2009 at 10:28 PM, Brian West wrote:
> Those configs will still work.
> /b
>
> On Sep 9, 2009, at 6:16 AM, Jörg Hartmann wrote:
>
> Hi there,
>
> the
Those configs will still work.
/b
On Sep 9, 2009, at 6:16 AM, Jörg Hartmann wrote:
Hi there,
the internal.xml and external.xml examples are for situations where
FS is running inside a company's private network, behind a NAT
router. So internal.xml connects the clients to FS without crossi
Hi there,
the internal.xml and external.xml examples are for situations where FS is
running inside a company's private network, behind a NAT router. So
internal.xml connects the clients to FS without crossing a NAT, within the
same private network, while external.xml connects SIP providers through
