Re: [Yxa-devel] Outgoingproxy doesn't seem to make a difference
Peter Krnjevic wrote: > I've no idea what I'm doing wrong, but whether "outgoingproxy" is > running or not seems to make no difference. > Phones that require NAT from my LAN appear in the location database with > the same ip address and port and all inbound calls are routed to the > first phone. Well, as Mikael Magnusson replied the outgoingproxy is primarily useful with TCP or TLS connections, although if a client registers using UDP and then keeps any NAT bindings open (by sending UDP keepalives) it should work as expected there too. Please check that the outgoingproxy is actually writing entrys to the location database itself, and not just routing the SIP REGISTER on to the incomingproxy. Besides that, it should work. I use it heavily myself although not with UDP clients... if it doesn't then please show some logs. /Fredrik ___ Yxa-devel mailing list Yxa-devel@lists.su.se https://lists.su.se/mailman/listinfo/yxa-devel
Re: [Yxa-devel] Outgoingproxy doesn't seem to make a difference
Peter Krnjevic wrote: > I've no idea what I'm doing wrong, but whether "outgoingproxy" is > running or not seems to make no difference. > Phones that require NAT from my LAN appear in the location database with > the same ip address and port and all inbound calls are routed to the > first phone. > Here are my incoming and outgoing proxy config files, if anyone has any > suggestions? > I'm also having constant problems trying to register a couple of > GrandStream GXP2000s - receiving authentication errors and refusing to > register, either directly connected to the Internet or on LAN > (192.168...). > And I've checked: the phones are pointing to port 5090 and the > transactions are showing up on "outgoingproxy". > Any and all suggestions welcome. > Best regards, > Peter Krnjevic > I think outgoingproxy is meant to be used with a connection oriented transport, TCP or TLS. Mikael ___ Yxa-devel mailing list Yxa-devel@lists.su.se https://lists.su.se/mailman/listinfo/yxa-devel
[Yxa-devel] Outgoingproxy doesn't seem to make a difference
I've no idea what I'm doing wrong, but whether "outgoingproxy" is
running or not seems to make no difference.
Phones that require NAT from my LAN appear in the location database with
the same ip address and port and all inbound calls are routed to the
first phone.
Here are my incoming and outgoing proxy config files, if anyone has any
suggestions?
I'm also having constant problems trying to register a couple of
GrandStream GXP2000s - receiving authentication errors and refusing to
register, either directly connected to the Internet or on LAN
(192.168...).
And I've checked: the phones are pointing to port 5090 and the
transactions are showing up on "outgoingproxy".
Any and all suggestions welcome.
Best regards,
Peter Krnjevic
[{incomingproxy, [{sipauth_realm, "123.123.123.123"},
{sipauth_password, "123456"},
{defaultroute, "sip1.mci.com"},
{logger_logbasename, "/var/log/incomingproxy"},
{internal_to_e164, [{"^00(.+)$", "+\\1"},
{"^0(.+)$", "+46\\1"},
{"^(.+)$", "+468\\1"}
]},
{e164_to_pstn, [{"^\\+468([1-9][0-9]+)$", "\
[EMAIL PROTECTED]"},
{"^\\+46([1-9][0-9]+)$", "[EMAIL PROTECTED]"},
{"^\\+44([1-9][0-9]+)$", "[EMAIL PROTECTED]"},
{"^\\+([0-9]+)$", "[EMAIL PROTECTED]"}
]},
{number_to_pstn, [{"^118$", "[EMAIL PROTECTED]"}]},
{enum_domainlist, ["e164.arpa"]},
{homedomain, ["mydomain.com"]},
{listenport, 5060},
{myhostnames, ["proxy1.mydomain.com"]},
{appserver, "appserver.mydomain.com:5070"},
{eventserver, "eventserver.mydomain.com"}
]}].
[{outgoingproxy, [{sipauth_realm, "123.123.123.123"},
{sipauth_password, "verysecret"},
{logger_logbasename, "/var/log/outgoingproxy"},
{sipproxy, "123.123.123.123"},
{databaseservers, ['[EMAIL PROTECTED]']},
{homedomain, ["mydomain.com"]},
{listenport, 5090},
{myhostnames, ["proxy1.mydomain.com"]}
]}].
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
https://lists.su.se/mailman/listinfo/yxa-devel
