[OpenSIPS-Devel] [opensips] failing to loose route sequential requests that are proto wss (#742)

Eric Tamme notifications at github.com
Tue Jan 5 18:40:58 CET 2016


On master commit 968a4e004ebf85687f864b885a1ad5dc6632f41a

If I place a call from a WSS client to a UDP client, then the UDP client hangs up, opensips will show the following log indicating that it cant identify the protocol.
```
Jan  5 12:35:23 voipphreaker /usr/local/opensips/sbin/opensips[9885]: DBG:rr:after_loose: Topmost route URI: 'sip:159.203.234.107;r2=on;lr;ftag=s6992f0ms9;did=e6a.94fb3f15' is me
Jan  5 12:35:23 voipphreaker /usr/local/opensips/sbin/opensips[9885]: WARNING:core:grep_sock_info: unknown proto 9
Jan  5 12:35:23 voipphreaker /usr/local/opensips/sbin/opensips[9885]: WARNING:rr:after_loose: no socket found to match 2nd RR [9][159.203.234.107:443]
```

I dug around in sock_info.c and net/trans.c to find how the protos list was populated, but I'm not able to immediately see whats wrong.  get_sock_info_list appears to be return 0, but it looks like the wss proto is in the list as proto 9 as the log indicates, so I'm not clear on whats going on.

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/742
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20160105/55b1763e/attachment.htm>


More information about the Devel mailing list