Re: [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-v...@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-v...@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  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@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>


-- 
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP option ping prioritization

[Anthony Holloway]

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-v...@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  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@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP option ping prioritization

[Anthony Holloway]

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  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [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  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  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 
> 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  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@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
>
> --
> Regards,
> Ki Wi
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP option ping prioritization

[Ryan Huff]

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 
> 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 
> 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 
> 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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip





--
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP option ping prioritization

[Ki Wi]

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  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  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@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>


-- 
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP option ping prioritization

[saranyan k]

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  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] SIP option ping prioritization

[Ki Wi]

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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip