<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 04/02/16 06:00, Scott Griepentrog
wrote:<br>
</div>
<blockquote
cite="mid:CACrpESbvQU8yA8Gq+z_UE7_OTzo6csa8q_kqh4QVk3FiD0L8BA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="color:#660000">For calls that
fail, even where early media is played, the call should
terminate with a 4xx or 5xx SIP response which to a certain
degree correlates to the nature of the actual failure. The
SIP error code is delayed until the media playback completes,
but should be no different whether or not early media is used
(for the same actual failure).</div>
<div class="gmail_default" style="color:#660000"><br>
</div>
<div class="gmail_default" style="color:#660000">Early media is
simply an audio stream for human consumption to explain the
failure. There should be no need to attempt to recognize it,
unless your ITSP is not terminating the call correctly.</div>
<div class="gmail_default" style="color:#660000"><br>
</div>
</div>
</blockquote>
I recently ran some analysis of early media messages found in
cellular networks by recording the calls and running it through
CMU-Sphinx. There are only a few types of early media messages per
network, to cover a raft of failures.<br>
<br>
But I always got a SIP error code back as well, the early media I
found tended to play for upto 20 secs then drop the call, then you
get the error code. It might not be a very descriptive error but its
still an error code, and the early media audio message is not always
very distinct either. In the GSM networks the GSM failure code is
more useful but still seems somewhat randomly assigned by the
provider, even including the odd temporary failures. <br>
<br>
You are not really worried about what the failure reason is, its the
caller who needs to decide - did I misdial, is the number really
disconnected, is their phone out of coverage etc, you just need to
try your next available network, if the caller hasn't already hung
up after hearing the message<br>
<br>
You could possibly examine the audio before you get an answer but
then you might get caught by some other system or PBX playing early
media before answer that isn't actually a failure.<br>
<br>
If your ITSP is not giving you an error code then you have an issue.
<br>
<br>
Cheers Duncan<br>
<blockquote
cite="mid:CACrpESbvQU8yA8Gq+z_UE7_OTzo6csa8q_kqh4QVk3FiD0L8BA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="color:#660000"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Feb 3, 2016 at 8:41 AM,
Olivier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:oza.4h07@gmail.com" target="_blank">oza.4h07@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>
<div>
<div>
<div>
<div>
<div>
<div>Hello,<br>
<br>
</div>
I'm trunking with an ITSP that, when
treating an outbound to an unknown
destination, either:<br>
</div>
- send a SIP error code (I can't be more
explicit, at the moment),<br>
</div>
- or cast a pre-recorded audio message using
Early Media.<br>
<br>
</div>
At the same time, I'm also trunking with Contact
Center solution which doesn't support Early Media.<br>
<br>
<br>
</div>
Beside asking my ITSP to treat calls consistently or
ask Contact Centerto support Early Media, is there
a way to configure Asterisk to unify both above
error treaments into a single one ?<br>
<br>
</div>
How can I best deal with error messages passed as
Early Media.<br>
<br>
</div>
Best regards<br>
</div>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a
moz-do-not-send="true" href="http://www.api-digital.com"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a></a>
--<br>
New to Asterisk? Join us for a live introductory webinar
every Thurs:<br>
<a moz-do-not-send="true"
href="http://www.asterisk.org/hello" rel="noreferrer"
target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a moz-do-not-send="true"
href="http://lists.digium.com/mailman/listinfo/asterisk-users"
rel="noreferrer" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr"><img moz-do-not-send="true" alt="Digium logo"
src="https://my.digium.com/images/graphics/digium_RGB_signature.gif"
style="color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;font-size:12px"
height="50" width="288">
<div>Scott Griepentrog<br>
Digium, Inc · Software Developer<br>
445 Jan Davis Drive NW · Huntsville, AL 35806 · US<br>
direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090<br>
Check us out at: <a moz-do-not-send="true"
href="http://digium.com" target="_blank">http://digium.com</a>
· <a moz-do-not-send="true" href="http://asterisk.org"
target="_blank">http://asterisk.org</a><br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>