22 Mar
2018
22 Mar
'18
11:26 p.m.
Thanks for Your suggestion. I'm however not sure that it will solve the
problem which is a TCP connection problem.
I solved the issue by sending the call back to the kamailio which
handles the registrations, and just let the other kamailio's do the
topoh module.
-------------------- Med Liberalistiske Hilsner ----------------------
Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49
Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 03/22/2018 10:24 AM, Daniel Tryba wrote:
On Wed, Mar 21, 2018 at 07:44:50PM +0100, Kjeld Flarup
wrote:
My own fault
Because I needed to be able to forward the call to multiple GSM numbers at
the same voip provider, I split the call onto several instances of Kamalio
to be able to create new call id's
As a result, the registers were made on one instance, and the invites on
another. That apparently worked fine most of the time, because Kamailio is a
proxy.
You maybe could fix this by using the Path module by storing the
proxy/registrar that received the call. If the endpoint registers
directly you might have to create your on path headers before save()
(atleast that was my conclusion for 4.3).
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users