[OpenSIPS-Users] websocket to post failure issues

[Răzvan Crainea]

Got your private message.

By default, OpenSIPS sends the request on the interface it received the 
message from. Therefore, if the request was sent from a WS client, then 
the same interface will be used to send it out.
If you'd like to send via UDP, you'll have to the force_send_socket() 
function in failure_route{} to change the outbound interfaces.

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 09/28/2015 03:34 PM, Răzvan Crainea wrote:
> Hi, Tito!
>
> I am not sure I understand your scenario. So you first send a message 
> to a client (is he a WS client?) and then, if that fails, you failover 
> to a different server(AS server, not WS)?
> Can you post OpenSIPS debugging logs on pastebin? You can email them 
> personally if you don't want to share them with the list.
>
> Best regards,
> Răzvan Crainea
> OpenSIPS Solutions
> www.opensips-solutions.com
> On 09/18/2015 02:36 AM, Tito Cumpen wrote:
>>
>> Group,
>>
>>
>> I am using opensips 2.2-dev git revision: 0faac6a and I am seeing 
>> issues when sending a request to second  route for failover 
>> purpose(AS server) When the source is a WS client. I am using sipjs 
>> version 0.7.1
>>
>> within this 2nd route i'm specifying (sip:ip:port) but opensips is 
>> sending this request as a websocket.
>>
>> which concludes in this error:
>>
>>
>> CRITICAL:proto_ws:ws_server_handshake
>>
>> Only when the request  goes from the failure route to the failover 
>> route. In the event that I route the request directly to the 2nd 
>> route upon failure to find the AOR entry for the user from the main 
>> route.  Opensips does send the request go to AS server as a sip 
>> request. Another note to add is that opensips does not revert the 
>> ruri . In the case of sipjs it utilizes a random string for contact 
>> entries upon registration. Opensips uses this as the ruri when making 
>> the request it does not revert them upon failure route consequently 
>> the request reaches  failover route with this ruri as well. Can I use 
>> revert_uri();
>>
>> in this case? within the failover route?
>>
>> What can be done over the fact that the request is being sent to the 
>> AS server as a ws?
>>
>>
>> What do you guys think about this strange error in the logs??
>>
>> " >>> not a new connection here 1
>>
>> It seems you have hit a programming bug.
>>
>> Please help us make OpenSIPS better by reporting it at 
>> https://github.com/OpenSIPS/opensips/issues"
>>
>>
>>
>> Thanks,
>>
>> Tito
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150929/1038f222/attachment-0001.htm>