Sunday, December 7, 2008

Re: [asterisk-biz] SIP Provider and relation to AMD Quality

AMD is not a turn on and it works solution, especially with cell phones. You will need to spend a good bit of time tuning it towards your target answering systems. Once tuned it works pretty well, there are also a number of people on this list that seem to sell AMD tuned systems, so they may show up or you can call out to them.

henry@henrythebig.com wrote:
We tried the AMD on T1 trunk with success rate on cell vm at 60% :( At that moment we use * 1.2.16. I will try on 1.6 to see the improvement.  Best regards,  Chris Hariga  ------Original Message------ From: Dave Greenroom Creations Sender: asterisk-biz-bounces@lists.digium.com To: Commercial and Business-Oriented Asterisk Discussion ReplyTo: Commercial and Business-Oriented Asterisk Discussion Subject: [asterisk-biz] SIP Provider and relation to AMD Quality Sent: Dec 5, 2008 4:20 PM  I'm still having a hard time getting asterisks' answering machine  detection to work as good as we hoped.   Now I'm wondering if theres  some connection with SIP providers and the AMD setup.  Perhaps with a  higher quality SIP provider  it would be a cleaner connection and make  it easier for the AMD to do it's job correctly.  Just an idea and was wondering if anyone had some input on this possible  connection.  Thanks, Dave   _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com--  asterisk-biz mailing list To UNSUBSCRIBE or update options visit:    http://lists.digium.com/mailman/listinfo/asterisk-biz   Sent from my BlackBerry® smartphone with SprintSpeed _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com--  asterisk-biz mailing list To UNSUBSCRIBE or update options visit:    http://lists.digium.com/mailman/listinfo/asterisk-biz    


--
Robin D. Rodriguez
Systems Engineer
Ifbyphone, Inc.
Phone: (866) 250-1663
Fax: (847) 676-6553
rrodriguez@ifbyphone.com
http://www.ifbyphone.com

 

 

No comments: