Missed that, thanks Razvaan!
Royee
On Fri, Dec 15, 2017 at 1:44 PM Răzvan Crainea wrote:
> Hi, Royee!
>
> As you can see in the logs, the route set is shrikend - so opensips cannot
> restore the entire information.
> Taking a look at the trace you have sent, it is clear that the client is
> not
Hi, Royee!
As you can see in the logs, the route set is shrikend - so opensips
cannot restore the entire information.
Taking a look at the trace you have sent, it is clear that the client is
not sending the second SUBSCRIBE with all the information:
* The 200 OK thinfo param has 154 chars
* Th
I have found something in the opensips.log that might shed some light:
/usr/sbin/opensips[27370]: DBG:topology_hiding:topo_no_dlg_seq_handling:
extracted routes [, found
I also see this when initially doing the topology hiding:
/usr/sbin/opensips[27370]: DBG:topology_hiding:topo_no_dlg_encode_c
Hi,
I am using opensips 2.1 and I'm experiencing some weird behavior with
SUBSCRIBE handling on an opensips server that is behaving as a SIP proxy. I
also use the topology_hiding module to hide routing information from the
clients.
The proxy receives an initial SUBSCRIBE from a device, the SUBSCR
