If you're using the 401 as an indication that it fails then you don't
understand how digest authentication works. I would have to see what happens
after the 401 to see if it really did fail.
/b
On Dec 24, 2009, at 5:16 AM, Mark Campbell-Smith wrote:
This is all I see and then registration
Can you get me siptraces please.
/b
On Dec 20, 2009, at 5:54 PM, Mark Campbell-Smith wrote:
Thanks Brian and Gad,
I have stun set and if I do a 'sofia status profile internal', I see
the external IP address of the 3102 ATA, so I assume that stun is
working correctly on the SPA3102.
Hi!
I'm sure this is a NAT issue, but I'm not sure what options to use.
I have a Linksys SPA3102, NAT'd on the internet (remotely) and
connected to my FS on the otherside of the world, which is also
natted. A PAP2T is connected on the same subnet as the FS. The 3102
registers successfully and
You'll need to fix your device to know its IP and it should stop doing that.
/b
On Dec 20, 2009, at 5:58 AM, Mark Campbell-Smith wrote:
Hi!
I'm sure this is a NAT issue, but I'm not sure what options to use.
I have a Linksys SPA3102, NAT'd on the internet (remotely) and
connected to my
DISCLAIMER: I'm REALLY new to
FreeSwitch, so please take my advice with a grain of salt.
I have a similar setup (and problem) - the wiki documentation refers to
it as "double nat". Like you, my FS and client are behind different
NATs and I can register my remote endpoint and make calls (in my
On Dec 20, 2009, at 2:53 PM, Gad Bentolila wrote:
DISCLAIMER: I'm REALLY new to FreeSwitch, so please take my advice with a
grain of salt.
Welcome to the community.
I have a similar setup (and problem) - the wiki documentation refers to it as
double nat. Like you, my FS and client are
Thanks Brian and Gad,
I have stun set and if I do a 'sofia status profile internal', I see
the external IP address of the 3102 ATA, so I assume that stun is
working correctly on the SPA3102.
These are the options that I have set (according to the 3102 manual).
• Handle VIA received: yes
•
