22 Jan
2013
22 Jan
'13
6:33 a.m.
Do no send replies to private address only, keep mailing list otherwise
future such emails will be discarded.
The contact has to stay the same, because it needs to be the address of
the device. Record-Route and Path are designed to take care of routing
back to lb, which will use tls to send to device.
Cheers,
Daniel
On 1/22/13 12:26 PM, Anton Kvashenkin wrote:
Thanks for reply. Yes, kamailio acts as a balancer
sending REGISTER
and INVITES, etc. The problem is that at L3-L4 it works well (sends
all datagram messages to 10.0.0.1:5060 <http://10.0.0.1:5060> UDP) but
at L7 the Contact header: <>;transport=tls.
2013/1/22 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
Hello,
On 1/22/13 10:56 AM, Anton Kvashenkin wrote:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
Guys, I've already asked @ G+ Kamailio
coummunity but had no
answer so I'm asking here:
I'm trying to deploy +Kamailio
<https://plus.google.com/114984922071338017631> as a front-end
for TLS-UDP translation, as a back-end would be +FreeSWITCH
<https://plus.google.com/104108080382960591162> . So, is kamailio
so smart to fix Contact or Path header for ;transport=tls or it
translates only on L3-L4 layer and I should fix those headers
manually?
is it only for calls or you need to forward registrations to
kamailio as well?
Everything is done automatically, for calls you just need to do
record routing. For registrations you have to use path module and
be sure that freeswitch supports sip path extension.
Cheers,
Daniel
--
Daniel-Constantin Mierla -http://www.asipto.com
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda>
-http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
-http://conference.kamailio.com -