<div dir="ltr">Hi Ki Wi,<div><br></div><div>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.</div><div>Otherwise, we can configure a keepalive profile so that we can specify the mode of transport for the OPTIONS keepalive messages. </div><div><br></div><div>!</div><div>
<p class="gmail-p1"><span class="gmail-s1">voice class sip-options-keepalive 1</span></p><p class="gmail-p1">transport tcp</p><p class="gmail-p1">!</p><p class="gmail-p1">Map the profile to any dial-peer:</p><p class="gmail-p1">!</p><p class="gmail-p1"><span class="gmail-s1">dial-peer voice 1 voip</span></p><p class="gmail-p1"><span class="gmail-s1"><span class="gmail-Apple-converted-space"> </span>session protocol sipv2</span></p><p class="gmail-p1"><span class="gmail-s1"><span class="gmail-Apple-converted-space"> </span>incoming called-number 299</span></p><p class="gmail-p1"><span class="gmail-s1"><b><span class="gmail-Apple-converted-space"> </span>voice-class sip options-keepalive profile 1</b></span></p><p class="gmail-p1"><span class="gmail-s1"><span class="gmail-Apple-converted-space"> </span>dtmf-relay rtp-nte sip-notify</span></p><p class="gmail-p1"><span class="gmail-s1"><span class="gmail-Apple-converted-space"> </span>codec g711ulaw</span></p><p class="gmail-p1">
</p><p class="gmail-p1"><span class="gmail-s1"><span class="gmail-Apple-converted-space"> </span>no vad</span></p><p class="gmail-p1"><span class="gmail-s1">!</span></p><p class="gmail-p1"><span class="gmail-s1">Say if the router is set to use UDP, its worth to give it a try with TCP.</span></p><p class="gmail-p1"><span class="gmail-s1">Please let me know if this helps.</span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">Regards,</span></p><p class="gmail-p1"><span class="gmail-s1">Saranyan</span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><br></p><p class="gmail-p1"><br></p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 28, 2017 at 8:26 AM, Ki Wi <span dir="ltr"><<a href="mailto:kiwi.voice@gmail.com" target="_blank">kiwi.voice@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Group, </div><div>I would like to find out if SIP option ping is a "ping" or a "sip message" ?</div><div><br></div><div>From the documents, it seems like it is a sip messages. </div><div><br></div><div>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. </div><div><br></div><div> Currently this is the command on all their managed "voice gateway" </div><div> * voice-class sip options-keepalive up-interval 120 down-interval 120 retry 2</div><div><br></div><div>This means the "transport" mode is default. This make things more complex, I have no idea it is TCP or UDP or ???</div><div><br></div><div>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? </div><span class="HOEnZb"><font color="#888888"><div><br clear="all"><br>-- <br></div><div class="m_-6032399500103171157gmail_signature"><div dir="ltr"><div>Regards,</div><div>Ki Wi</div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>