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
* The SUBSCRIBE thinfo has only 55 chars
I would check whyt the client is not using the entire thinfo param.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 12/14/2017 06:41 PM, Royee Tichauer via Users wrote:
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
[<sip:54.165.144.73;lr>,<sip:qa7vqblfc1c] , ct [] and bind []
Dec 14 16:17:00 qa7vqsbc4.qa7.vocal-qa.com
<http://qa7vqsbc4.qa7.vocal-qa.com> /usr/sbin/opensips[27370]:
ERROR:core:parse_nameaddr: no > found
I also see this when initially doing the topology hiding:
/usr/sbin/opensips[27370]:
DBG:topology_hiding:topo_no_dlg_encode_contact: Trying to propagate
username [blf]
/usr/sbin/opensips[27370]: DBG:core:parse_headers: flags=ffffffffffffffff
/usr/sbin/opensips[27370]: DBG:core:print_rr_body: current rr is
<sip:qa7vqblfc1ctrl1.qa7.vocal-qa.com
<http://qa7vqblfc1ctrl1.qa7.vocal-qa.com>;lr>
/usr/sbin/opensips[27370]: DBG:core:print_rr_body: current rr is
<sip:54.165.144.73;lr>
/usr/sbin/opensips[27370]: DBG:core:print_rr_body: out rr
[<sip:54.165.144.73;lr>,<sip:qa7vqblfc1ctrl1.qa7.vocal-qa.com
<http://qa7vqblfc1ctrl1.qa7.vocal-qa.com>;lr>]
On Thu, Dec 14, 2017 at 5:45 PM Royee Tichauer
<[email protected] <mailto:[email protected]>> wrote:
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
SUBSCRIBE doesn't contain a "to tag" so I process it like a normal
SUBSCRIBE message and route it to the correct route which replies
with a 200 OK with a "to tag". Some time before the expiration of
the SUBSCRIBE is passed I receive a another SUBSCRIBE, this time
with a "to tag" so my opensips config file attempts to match it to
a topology matching but for some reason it fails to match it.
I have this configured:
modparam("dialog", "dlg_match_mode", 0)
Any idea why the second subscribe message is not being matched?
Attached is a capture of the initial and following subscribes.
Thanks,
Royee
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
