Hi Gang
A quick search via google did not reveal any useful hits.
Kamailio 5.7.6
CPE (TLS) => SBC (UDP) => Registrar (UDP) => Core
CPE uses a sips contact URI to register, no transport attribute!
sips:315996608@172.29.255.11:5061
SBC uses Path functionality.
Situation: Call to CPE
I see the registrar adding this Record-Route:
Record-Route: <sips:registrar-ip;lr;ftag=6159862378>
The SBC is adding a r2=on Record-Route to indicate the change between
UDP and TLS.
The Route-Set received by the CPE then is:
INVITE sips:315996608@172.29.255.11:5061 SIP/2.0
Record-Route: <sips:sbc-ip:5061;transport=tls;r2=on;lr;ftag=6159862378>
Record-Route: <sips:sbc-ip;r2=on;lr;ftag=6159862378>
Record-Route: <sips:registrar-ip;lr;ftag=6159862378>
Record-Route: <sip:core-ip;lr;ftag=6159862378>
180 Ringing req 100rel is making it back as the Via header look right.
But when the remote side is sending a PRACK, is has to follow the
Routeset which if I am not mistaking, is not making it back because
because the CORE does not know how to send this via TLS to the
Registrar.
Core logging:
prepare_new_uac(): can't fwd to af 2, proto 3 (no corresponding listening socket)
IMHO already the 2nd Record-Route added by the Registrar should not
contain a sips: URI but a sip: URI (reflecting the transport attribute
not being present, defaulting to UDP)
Is this a known issue?
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Hello all,
As in previous years, I'm organising the VoIP dinner for FOSDEM (1 Feb @
19:00)
However unlike previous years (since the restaurant got upset about
splitting the bill 30 ways). I will ask everyone to order their meal and
pay in advance. (and I will pay the bill to the restaurant with my card)
If you are wanting to attend the dinner please fill out the following form
and follow the instructions for payment.
https://form.jotform.com/250012543310033
Contact details are also in the form if you want to reach out to me with
any further questions.
Kind regards
Torrey
Dear Kamailio Team,
I hope this email finds you well.
I am currently working on a project where Kamailio is being utilized as a
load balancer to distribute calls across multiple FreeSWITCH instances. I
am using the round-robin technique for load distribution, and it is working
perfectly for regular call scenarios.
However, I am encountering an issue when handling attended transfer calls.
Specifically, for a normal call, Kamailio assigns one FreeSWITCH instance,
but during the attended transfer call, it assigns another FreeSWITCH
instance. This behavior disrupts the continuity of the call handling.
My requirement is for Kamailio to use the same FreeSWITCH instance for the
entire call, including any attended transfers. I believe maintaining the
same FreeSWITCH instance for the entire call flow would ensure consistency
and avoid potential issues.
Could you please guide me on how to configure Kamailio to achieve this
behavior? I would greatly appreciate any suggestions, configurations, or
modules that can help resolve this issue.
Thank you for your time and assistance.
Looking forward to your response.
Best regards,
Kotappa Y Gandudi