On 07 Nov 2014, at 18:02, Jon Bonilla (Manwe) wrote:
> Hi all
>
> I'm experiencing a problem while using a mobile client on a NGCP mr3.5.1
> (based
> on kamailio 4.1.6)
>
> The problem is as follows:
>
> A custom mobile client
> B blink for linux
>
> The path of a call from B to A would be
Hello,
I think the rule is that if the r-uri is enforcing sips, then record
route has to be sips.
In general, sips is a mess, because the rule is: it has to be
transmitted over something secure (which can be udp via vpn, or udp in a
private network, etc.).
You can probably fix it in the config.
Hi all
I'm experiencing a problem while using a mobile client on a NGCP mr3.5.1 (based
on kamailio 4.1.6)
The problem is as follows:
A custom mobile client
B blink for linux
The path of a call from B to A would be this one:
B --> Kamailio LB --> Kamailio proxy --> Sems --> Kamailio LB --> A
