<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
In general, I advise my clients to <b>not </b>generate ringback
tone on phones. Best practice is to have phones indicate alerting
state by responding with 180 RINGING with no SDP, and require PRACK
method. Media flow from phones <i>before </i>200 OK may cause
other problems, especially in a simultaneous ringing environment.
<br>
<br>
One common practice is that 180 RINGING is sent without SDP, and a
media gateway closer to the caller furnishes the ringback tone.
PRACK is optionally used to ensure that the provisional response is
reliable. Another common practice is to send 183 PROGRESS with
SDP indicating the availability of early media and progress tone,
but that practice isn't bullet proof. <br>
<br>
Hope this helps. If you would like additional discussion, please
feel free to contact me off list.<br>
<br>
<blockquote>John S. Robinson<br>
<i><a href="mailto:jsr@communichanic.com">jsr@communichanic.com</a></i><br>
Communichanic Consultants, Inc.<br>
<br>
</blockquote>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/5/2012 23:40, John Botha wrote:<br>
</div>
<blockquote cite="mid:BAY150-ds1623B474E292DC2DF5707BC6B0@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">We are debating on having our Broadsoft
media server generating RBT on a SIP 180 vs having the phone
generate it locally, which is currently the case.<o:p></o:p></p>
<p class="MsoNormal">We have found sporadic ringback issues when
the phones generate local RBT when it plays one ring and then
goes silent or no RBT at all. This only happens once out of
approximately 10 calls though, and signalling looks normal (ie
no 180 followed by 183 or duplicate messaging).<o:p></o:p></p>
<p class="MsoNormal">The end-user hardware devices are mostly
Polycom.<o:p></o:p></p>
<p class="MsoNormal">Does anyone have some experience, advice
and information this? <o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
</body>
</html>