Do you have the UIP200 working behind nat when you have nat=never set? I've only been able to connect from the same IP range when I have nat=never set.
I can connect with nat=yes from behind nat, but it won't stay connected.
I'm using CVS-HEAD-08/24/04-10:03:52


Ryan Courtnage wrote:

spectro wrote:

- You MUST use nat=never in sip.conf. The UIP200 does not like rfc3581
(rport), and will not reply to requests that contain it.  Using
'nat=never' in sip.conf disables *'s support for this rfc.  Uniden has
acknowledged the issue (DR#60).


Are you running RC1 or RC2?. We are running a pre-RC1 version of * and
nat=yes works fine. After we upgraded to RC2 we were unable to call
the UIP200 extension.


Do you have nat=never with your RC2?

I use CVS-D2004.06.29.15.30

Here's the bug that introduced rfc5581 support:
http://bugs.digium.com/bug_view_page.php?bug_id=0001862

And here's the bug that made it optional:
http://bugs.digium.com/bug_view_page.php?bug_id=0001935


_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users



_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to