[cisco-voip] SIP option ping prioritization

[Anthony Holloway]

Just to clarify, UDP is default in CUBE and TCP is default in CUCM.

Actually, we should further clarify that by saying, these are the default
transport protocols for SIP UAC messages.  If either product were to
receive either UDP or TCP, it will respond with the same transport
protocol.  I.e., It wouldn't make sense to receive a UDP packet, and then
reply with TCP packet.

And I have to agree with Ryan that ACLs would not allow you to look at the
SIP Request line to determine if it's an OPTIONS dialog as opposed to an
INVITE or SUBSCRIBE.  Just treat all SIP the same, and by that I mean,
treat it like your typical signaling traffic.  CUBE does AF31 still, so you
might want to switch it to CS3 on your dial-peers or just have a Match-Any
with AF31 and CS3 in your class map.

On Mon, Aug 28, 2017 at 1:43 AM Ryan Huff <ryanhuff at outlook.com> wrote:

> The OPTIONS Ping will come across in the regular SIP stack
> (TCP:5060/TCP:5061 or UDP:5060 typically). Prioritization is a Quality of
> Service technique and not an Access Control technique. I don't think a
> standard ACL would look at the application layer header to differentiate
> SIP messages and offer priority of individual SIP messages.
>
> I'd look into making sure you are applying the correct signaling QoS to
> the ingress/egress links.
>
> -RH
>
> On Aug 27, 2017, at 11:31 PM, Ki Wi <kiwi.voice at gmail.com> wrote:
>
> Hi Saranyan,
> thanks! I would like to know how can I compose an access-list to detect
> SIP option ping and prioritize it.
>
>
>
>
> On Mon, Aug 28, 2017 at 11:20 AM, 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
>>>
>>>
>>
>
>
> --
> 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/7be1f572/attachment.html>