25 Oct
2012
25 Oct
'12
11:26 p.m.
25 okt 2012 kl. 22:07 skrev Klaus Darilion <klaus.mailinglists(a)pernau.at>at>:
Indeed, just use a timer route to periodically send
OPTIONS to the registrar.
Are you looping outgoing messages also through the registrar? Or does the request to the
obp with has 2 Route headers?
I have an ingres proxy behind NAT that adds a path header and sends the register to a
proxy on a public IP. this one adds another PATH with received and loops back to itself
before saving the location.
When calling, the INVITE will get two Route headers (based on the PATH headers), one to
get back to the TCP connection and the other one back over that connection to the ingres
proxy. Klaus-style, routing on received.
Of course, it's easy to add TLS in this scenario. I will soon test your Asterisk patch
for Path (the Oolong-branch now) and see if it can play in this setup as well.
Good night.
/O
K
Am 25.10.2012 um 21:57 schrieb "Olle E. Johansson" <oej(a)edvina.net>et>:
> Hi!
>
> THanks, Klaus!
>
> The solution was to use a trick by Peter Dunkley in an old mail. I could add another
Path header, but could not run msg_apply_changes on that. Instead I forwarded the message
to myself and then saved in location database. Now I have to path headers, with the top
one pointing to the TCP connection with the received parameter, like you described.
>
> Thanks for explaining the TCP connection matching and your open brainstorm that
provided a solution!
>
> The question is now how to get the proxy on the inside of the NAT - also Kamailio -
to keep the TCP connection open for a very, very long time :-)
> But there are many TCP parameters for that. And NAT keepalives.
> /O