Asterisk is unique in the sense that you get a G723 call and you may connect it out with Ulaw provider, a G729 carrier, and the reverse is also true. There are many technologies that deal only with signaling, but I have not found a clear alternative to Asterisk when you consider the codecs and transcoding issues. Also I get one call in, and start dialing all the carriers on the order of price, from cheapest to the most expensive. So I need a complete separation of the inbound channels and the outbound channel. Maybe somebody can recommend how to do these tricks away from Asterisk. I don't think it is possible. <div>
Version 1.6X with a new feature found in Trunk (Q850 relay on the BYE) make Asterisk into a Class 5. If we can solve this bug that I reported several months ago.</div><div><br></div><div>Yours</div><div><br></div><div>Federico<br>
<br><div class="gmail_quote">On Thu, Feb 25, 2010 at 9:44 PM, Geoffrey Mina <span dir="ltr"><<a href="mailto:geoffreymina@gmail.com">geoffreymina@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Why not route your calls through an OpenSIPS or Kamailio server?<br>
These both have the ability to fail over very quickly if no<br>
provisional 1XX response is received... Plus you wouldn't have to<br>
build failover into asterisk. Which is a good thing as SIP failover<br>
has no place in the dialplan.<br>
<div><div></div><div class="h5"><br>
On 2/25/10, Olle E. Johansson <<a href="mailto:oej@edvina.net">oej@edvina.net</a>> wrote:<br>
><br>
> 25 feb 2010 kl. 17.46 skrev Kevin P. Fleming:<br>
><br>
>> Tim Ringenbach wrote:<br>
>>> If "first ring" is what you want, you would probably not want to count<br>
>>> 100's, only 183 or 180. For example. OpenSips automatically sends back a<br>
>>> 100 trying when you sent it a call, before it even passes the packet on<br>
>>> to it's destination. It then absorbs the 100 Trying it gets from the far<br>
>>> end.<br>
>><br>
>> All SIP UAS endpoints must send 100 Trying in response to an INVITE as<br>
>> quickly as they can do so (and for other sorts of requests as well).<br>
>> Asterisk does this now.<br>
><br>
><br>
> All proxys has to send a 100 trying to say "I've got it and I'm trying to<br>
> proxy this message through". At that point, we stop retransmitting stuff,<br>
> since we've got someone acting on our behalf. That's why the proxy send 100<br>
> trying by itself and swallow the one received from the other side, if<br>
> received.<br>
><br>
> /O<br>
><br>
><br>
><br>
><br>
> --<br>
> _____________________________________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> asterisk-dev mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
><br>
<br>
</div></div><font color="#888888">--<br>
Sent from my mobile device<br>
</font><div><div></div><div class="h5"><br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br></div>