[cisco-voip] SIP option ping prioritization

[Ki Wi]

Hi All,
thanks ! Got it. We already have acl matching tcp 5060 and udp 5060. TLS is
not used in our environment so tcp 5061 is not included.

Looks like they will need to investigate on the CAC as we place signaling
and voice into the same queue. ( Only 5 class of service in WAN)




On Tue, Aug 29, 2017 at 1:23 AM, Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> I should have also mentioned that interface binding is very important not
> only from where you'll source your OPTIONS messages, but also from where
> you'll reply to them.  I've seen the layer 4 and down be correct due to
> where the OPTIONS was received, but then layer 5 was displaying a different
> IP address.  Make sure you bind on all dial-peers, but you only need
> OPTIONS configured on outgoing dial-peers.
>
> On Mon, Aug 28, 2017 at 12:12 PM Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> 1) It's a SIP Message, specifically the OPTIONS message
>>
>> 2) Typically you only prioritize voice traffic and not signaling, but you
>> should still reserve bandwidth for signaling to ensure it's not starved.
>> CUBE marks all signaling traffic as AF31 by default, but CS3 is the newer
>> standard to go with.  Make sure you're QoS policy is matching on AF31
>> and/or CS3 and reserving bandwidth for it.
>>
>> 3) In the absence of a session transport command, the default is UDP,
>> that's typical for carrier facing SIP trunks.
>>
>> 4) I have not seen OPTIONS prioritized before. It's treated with the
>> level of service as all SIP and therefore all signaling
>>
>> On thing people forget is to use a profile on dial-peers which reference
>> server groups.
>>
>> See here for a little more info on that:
>> https://supportforums.cisco.com/t5/video-over-ip/sip-
>> options-ping-and-session-server-group-on-dial-peer/td-p/2994584
>>
>>
>> On Sun, Aug 27, 2017 at 9:56 PM 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170829/07425666/attachment.html>