<div>I need information about integration of Asterisk and Avaya 70XX, if you have a configuration this sistems, please send me the informatión.</div>
<div> </div>
<div>Sorry for my english, i speeck spanish!!!!.</div>
<div> </div>
<div>Atte,</div>
<div>Rodrigo Mercado Sepúlveda.</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 7/20/06, <b class="gmail_sendername">Maxx Lobo</b> <<a href="mailto:maxx@arraycomm.com">maxx@arraycomm.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">An update:<br><br>I've found that I can leave the TE110P card in the server, unload the<br>module and issue an 'amportal restart' - this brings the
<br>IVR/meetme/internal directory voice prompts all back again.<br><br>So it looks like the issue is directly related to the TE110P module<br>(wcte11xp) in kernel 2.6.9.34-0.2 with CentOS 4.3. Anyone else<br>experience this issue or have any suggestions based on this new information?
<br><br>Thanks-<br><br>--Maxx<br><br>Maxx wrote:<br>> I've developed an issue I was hoping someone on this list might be able<br>> to shed some light on.<br>><br>> I have two identical asterisk servers: CentOS
4.3, single TE110P card.<br>> I've also got a SIP trunk configured with TelaSIP for in/out calling.<br>> Both boxes have been running the same versions of Asterisk, Zaptel, etc.<br>> In short, no difference between the two. One box is the primary system,
<br>> all of the SIP clients on the network associate to it. I'll call this<br>> one PBX01. The other box, PBX02, is a test platform to install new<br>> releases on, and to make sure everything works as before before any
<br>> upgrades take place (and new bugs get introduced ;-))<br>><br>> The plan was to get the system up and running using a VoIP trunk, then<br>> cut the T1 line over to the Digium TE110P card and keep the VoIP trunk
<br>> as a backup for emergencies.<br>><br>> Originally both boxes were running A@H 2.7, and there were no issues. I<br>> upgraded to A@H 2.8, and got hit by the spinlock.h kernel issue as a<br>> result of a yum update. No big deal, ran the fixes, everything seemed to
<br>> work okay. VoIP trunk still in place. There were no errors with zaptel,<br>> and the module for the TE110P was detected on boot. Absolutely no<br>> asterisk errors either.<br>><br>> Then I noticed that any voice menu-related items were broken - IVR menu
<br>> was broken when outside callers called the VoIP trunk number, Meetme<br>> conferencing calls were also 'broken' in that there was nothing but<br>> silence when I called a working conference number, and internal
<br>> directory calls to 7777 were also receiving dead air.<br>><br>> I tried a number of things, none of which worked - so on a whim, I<br>> removed the TE110P. Amazingly, everything worked fine when the box<br>
> restarted. Meetme conferencing, external calls, internal directory,<br>> everything.<br>><br>> Thinking that the card may have developed hardware issues, I tried the<br>> TE110P from the standby server (PBX02). The same issues returned right
<br>> away.<br>> So then I tried swapping servers, to make sure there weren't some<br>> hardware issues cropping up. Same result again - worked fine without the<br>> TE110P, did not work with it.<br>> Now I tried upgrading the test box to Trixbox
1.1, and upgrading the<br>> zaptel to 1.2.7 from source. Same issues all over again.<br>><br>> I've seen the suggestions on Kennonsoft<br>> <<a href="http://www.kennonsoft.org/2006/07/trixbox-v10-quickie-how-to.htm">
http://www.kennonsoft.org/2006/07/trixbox-v10-quickie-how-to.htm</a>> about<br>> the meetme conferencing directory permissions, and I've made all of<br>> those changes. It didn't work before the changes or after - same problem
<br>> all along.<br>><br>> The modules are getting loaded fine as evidenced by lsmod:<br>> --------<br>> [root@pbx01 asterisk]# lsmod<br>> Module Size Used by<br>> wcte11xp 30496 0
<br>> zaptel 196740 3 wcte11xp<br>> crc_ccitt 6081 1 zaptel<br>> --------<br>> No asterisk errors in the logs, either. No build errors when rebuilding<br>> zaptel-1.2.7. I've tried both kernel
2.6.9.34-0.1 and 2.6.9.34-0.2<br>> (currently running the latter on both servers). I can post the full logs<br>> if necessary.<br>><br>> The servers had sound cards in them, I removed these and made sure they<br>
> were removed from both modprobe.conf and by kudzu. I didn't think this<br>> was the issue, but it was sound related and I am grasping at straws.<br>><br>> Please tell me I'm missing something basic and what I can do to fix it.
<br>> Without the TE110P cards I can't cut things over as I intended to, and<br>> I'm all out of ideas on this.<br>><br>> Thanks-<br>><br>> --Maxx<br>> _______________________________________________<br>
> --Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>><br>> asterisk-users mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-users mailing list
<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br>