Hi Sergey,
Thank you for the tip. I'm going to try topoh but not now.
The question is: is there a bug in freeswitch or bug in my kamailio's
config. And it seems to me that there is a bug in freeswitch. I see in Via
my SIP proxy without transport=tls. And as per RFC freeswitch must use
transport w
Hi, Vladislav
I had very simmilar issue, try to use topoh module.
It will mask contact in header and called side will not try to send reply
to contact dyrectly or using its proto.
It will send using via or record-route headers.
But this will work when kamailio is in statefull proxy mode.
29 нояб.
Ouch... It didn't work for me as expected. I forgot that I have configured
FreeSWITCH to work with TLS.
When I reverted sofia profile to work only over UDP originating call fails
again with message:
[ERR] sofia_glue.c:943 TLS not supported by profile
2016-11-29 0:21 GMT+02:00 Vladyslav Zakhozha
Daniel, Alex, thank you for your answers.
FreeSWITCH works with path as expected and it is my solution. add_path and
add_path_received works fine in kamailio's config.
2016-11-28 19:02 GMT+02:00 Vladyslav Zakhozhai :
> That is very interesting.
>
> I've added add_path_received in Kamailio conf
That is very interesting.
I've added add_path_received in Kamailio config. And I can see that
FreeSWITCH received it and reflected in registration info.
With SIP/UDP there is no problems. FreeSWITCH gets path and respnses and
INVITEs goes through Kamailio.
But in case of TLS INVITES goes to Kama
On Mon, Nov 28, 2016 at 01:15:03PM +0100, Daniel Tryba wrote:
> > UAC == SIP/TLS ==> Kamailio == SIP/UDP ==> FreeSWITCH
> >
> solution is to use Path on the frontend/loadbalancer.
According to this closed bug report it should work for
Kamailio/Freeswitch:
https://freeswitch.org/jira/si/jira.issue
Path is indeed the exact solution for this type of problem.
-- Alex
--
Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-ro
On Mon, Nov 28, 2016 at 01:00:37PM +0200, Vladyslav Zakhozhai wrote:
> UAC == SIP/TLS ==> Kamailio == SIP/UDP ==> FreeSWITCH
>
> My main problem is in Contact header of SIP packet which passes through
> Kamailio SIP proxy and remains unmodified.
>
> For example, REGISTER request. There is FreeSWI
Hi,
I'm trying to understand the best (or reasonable) approach of offloading
SSL encryption from backend to Kamailio. Let me simplify a little bit:
UAC == SIP/TLS ==> Kamailio == SIP/UDP ==> FreeSWITCH
My main problem is in Contact header of SIP packet which passes through
Kamailio SIP proxy and
