[OpenSIPS-Users] sending sip options

[Arsen]

Michel,

Why do you care about the response from the remote server, in case if the
server is not under your control there it not much you can do about that.

I guess that the probing purpose in your scenario is to monitor the status
of the remote gateway. Since the server does respond to the SIP requests
means it is up and you can add 400 to the "probing_reply_codes" list.


Arsen Semionov
www.eurolan.info
cell: +442035198881

On Tue, Oct 10, 2017 at 12:30 PM, Michel crans <mcrans at gmail.com> wrote:

> Hi Arsen,
>
> Thank you for the quick responce
> I am using the options as probing method on the load balancer
>
> ### LoadBalancer module
> loadmodule "load_balancer.so"
> modparam("load_balancer", "db_url", "mysql://opensips:abcdefghr@
> 127.0.0.1:3307/opensips")
> modparam("load_balancer", "probing_interval", 10)
> modparam("load_balancer", "probing_method", "OPTIONS")
> modparam("load_balancer", "probing_from", "x.x.x.x")
>
>
> 2017-10-10 11:13 GMT+02:00 Arsen <arsen.semionov at gmail.com>:
>
>> Hi Michel,
>>
>> Proxy server never generates OPTIONS requests, do you use a probing like
>> in mod dispatcher (ds_ping_method) ?
>>
>> "400 Bad Request" indicates that the request was not understood by the
>> server, it could be due to missing of the required header for example, but
>> in your case the request has all required headers.. maybe the issue is on
>> the remote side..
>>
>> Regards,
>>
>> Arsen Semionov
>>
>>
>> On Tue, Oct 10, 2017 at 11:29 AM, Michel crans <mcrans at gmail.com> wrote:
>>
>>> Hi,
>>> when i send from opensips an option request i receive a 400-bad request.
>>> I guess this is because its missing the contact header ( wich i dont
>>> need according the sip rfc)
>>>
>>>
>>>
>>> 09:36:19.551613
>>>
>>>     vsipproxy01.local.sip > sbc02.local.sip: [bad udp cksum 0x3c1d ->
>>> 0x1818!] SIP, length: 337
>>>
>>>         OPTIONS sip:x.x.x.x SIP/2.0
>>>
>>>         Via: SIP/2.0/UDPy.y.y.y:5060;branch=z9hG4bKc3cc.ef1bf0e.0
>>>
>>>         To: sip:x.x.x.x
>>>
>>>         From: <y.y.y.y>;tag=6fdf67c715032fa03eb7e6e879881122-9108
>>>
>>>         CSeq: 10 OPTIONS
>>>
>>>         Call-ID: 0afc4f6a31598fc1-6433 at y.y.y.y
>>>
>>>         Max-Forwards: 70
>>>
>>>         Content-Length: 0
>>>
>>>         User-Agent: OpenSIPS (2.2.5 (x86_64/linux))
>>>
>>>
>>> 09:36:19.551965
>>>     sbc02sig.local.sip > vsipproxy01.local.sip: [udp sum ok] SIP,
>>> length: 291
>>>         SIP/2.0 400 Bad Request
>>>         Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bKc3cc.ef1bf0e.0
>>>         From: <172.23.113.66>;tag=6fdf67c715032fa03eb7e6e879881122-9108
>>>         Call-ID: 0afc4f6a31598fc1-6433 at y.y.y.y
>>>         CSeq: 10 OPTIONS
>>>         To: <sip:172.23.113.65>;tag=3716609745-661445930
>>>         Content-Length: 0
>>>
>>>
>>> help is much appriciated.
>>>
>>> regards
>>>
>>> Michel
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> 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/20171010/c2ecbe11/attachment-0001.html>