<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1">Hi Jeff,<br>
<br>
The B2BUA is a signaling function, not necessarily an IP layer
function. Yes, some SBCs may give you the ability to modify the
TTL but I'd look more at the Gateway/IP Phone configuration.<br>
<br>
What is the TTL being sent out by the end device? Some of those
are defaulted to absurdly low TTL, I've seen as low as 16. In
general that is where they configuration should be changed.<br>
<br>
~Glen<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 2/11/2019 7:04, Jeff Anderson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPz3n-zNX1RG51orNmtRD=0RRNL+wvod2a=AwSXBzUF-GyfcmQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">We are occasionally running into a situation where
our IP Header TTL expires in transit for RTP streams. It has
been our observation that our SBC B2BUA that anchors media is
not resetting the TTL on RTP packets but is on SIP packets.
<div><br>
</div>
<div>Is there a standard expected behavior for how SBC B2BUA
with media anchoring might handle RTP packets? I would have
thought if it resets the SIP packet TTL it would also reset
the RTP packet TTL.</div>
<div><br>
</div>
<div>Thoughts?</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Glen Gerhard
<a class="moz-txt-link-abbreviated" href="mailto:glen@cognexus.net">glen@cognexus.net</a>
858.324.4536
Cognexus, LLC
7891 Avenida Kirjah
San Diego, CA 92037
</pre>
</body>
</html>