[cisco-voip] SIP option ping prioritization

[Anthony Holloway]

Why does your example have options ping on an incoming dial-peer?  Since
there is no peer address configured, ping wont actually do anything.

Also, most carriers will required UDP, which is what CUBE does by default.

On Sun, Aug 27, 2017 at 10:20 PM saranyan k <saranyan2008 at gmail.com> wrote:

> Hi Ki Wi,
>
> OPTIONS ping is a SIP message. Ideally the transport mode of the message
> is TCP or UDP based on the configuration done under voice service voip ->
> sip.
> Otherwise, we can configure a keepalive profile so that we can specify the
> mode of transport for the OPTIONS keepalive messages.
>
> !
>
> voice class sip-options-keepalive 1
>
> transport tcp
>
> !
>
> Map the profile to any dial-peer:
>
> !
>
> dial-peer voice 1 voip
>
>  session protocol sipv2
>
>  incoming called-number 299
>
> * voice-class sip options-keepalive profile 1*
>
>  dtmf-relay rtp-nte sip-notify
>
>  codec g711ulaw
>
>  no vad
>
> !
>
> Say if the router is set to use UDP, its worth to give it a try with TCP.
>
> Please let me know if this helps.
>
>
> Regards,
>
> Saranyan
>
>
>
>
>
> On Mon, Aug 28, 2017 at 8:26 AM, Ki Wi <kiwi.voice at gmail.com> wrote:
>
>> Hi Group,
>> I would like to find out if SIP option ping is a "ping" or a "sip
>> message" ?
>>
>> From the documents, it seems like it is a sip messages.
>>
>> My customer is facing issue with the dial-peers getting busy out during
>> WAN congestion. We would like to prioritize those messages as a WAN
>> provider but they are not able to give us the exact commands for the CE
>> router.
>>
>>  Currently this is the command on all their managed "voice gateway"
>>  * voice-class sip options-keepalive up-interval 120 down-interval 120
>> retry 2
>>
>> This means the "transport" mode is default. This make things more
>> complex, I have no idea it is TCP or UDP or ???
>>
>> With no access to customer network (unable to do wireshark), I would like
>> to see if there's anyone having the experience to prioritize those SIP
>> option ping packets?
>>
>>
>> --
>> Regards,
>> Ki Wi
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170828/4339b029/attachment.html>