similar to: How to properly use GROUP

Dearest List, I guess I missed this point: Is it true that if you change the echo canceler in zconfig.h, and then recompile/install your zap modules, that for this to be taken into effect by * you must then recompile/install *? I would have figured that the zap echo cancellation method was independent of *, and I don't recall seeing any docs mentioning either way. Sincerely, Brent A.

Howdy: Does echo only occur on analogue PSTN lines, or can it also occur on PRI and BRI lines? If so, for the same reasons? This is a part of our consideration to transition to BRI. Sincerely, Brent A. Torrenga brent.torrenga@torrenga.com Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 219.836.8918x325 Voice 219.836.1138 Facsimile www.torrenga.com

Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 hours or so. Since upgrading to 1.2.3, though, the whole system has locked up twice. Once on Thursday, and then about a half hour ago. The server would reply to a ping, but no ssh login, no local console login - just locked up. This ain't good for

I use Cisco 7940's and 7960's over here, loaded with SIP, and they do very nicely. Also, the SCCP channel for * is under heavy development, and may offer a future option to convert in that direction, too (SCCP, or skinny, is their native tongue, not SIP). We got our phones from John Putnam at Global Technology Solutions - competitive price, very prompt service, and delivered them with the

Well, I thought and hoped my issue of random hangups on our TDM400P were related to busydetect=yes in zapata.conf. The behavior of a call being hungup has not changed, however, since setting the busydetect option to 'no'. Again, the only affected user is my loud talker... What are some causes/solutions to seemingly random call disconnects on Zap channels that people have seen? I have

Paul, Ah, I see. Our echo is largly under control now. It took me a while to figure out the gains and get them tuned, and now the echo only leaves very small artifacts. Nonetheless, this still provokes the odd complaint here and there. We use VOIP for outgoing calls when our POTS lines are congested, and we find zero echo during those calls. Therefore, I assume that our handsets (Cisco

>Our user places a call, the gateway responds with no sound at all, or >hangs up, or gives busy tone. > >How can we get to the next provider? > >I have now: >exten => _9011Z.,103,Dial(SIP/011${EXTEN:4}@provider-a) >;exten => _9011Z.,103,Dial(SIP/011${EXTEN:4}@provider-b) >;exten => _9011Z.,103,Dial(SIP/011${EXTEN:4}@provider-c) >exten =>

Anyone ever seen MeetMe cause * to crash? Specifically, it happens consistantly if someone begins to enter a conference and then decides to hangup while Allison is introducing them - like playing back "conf-onlyperson". This has been seen with the MeetMe participant connecting via IAX and SIP (not saying it doesn't happen with Zap, just that I haven't seen it). The box is *

I use Cisco 7940's and 7960's over here, loaded with SIP, and they do very nicely. Also, the SCCP channel for * is under heavy development, and may offer a future option to convert in that direction, too (SCCP, or skinny, is their native tongue, not SIP). We got our phones from John Putnam at Global Technology Solutions - competitive price, very prompt service, and delivered them with the

Howdy, How can you tell if RTP traffic has been reinvited/is bypassing an * server? Sincerely, Brent A. Torrenga brent.torrenga@torrenga.com Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 +1 219 836 8918 x325 Voice +1 219 836 1138 Facsimile www.torrenga.com

Has anyone had problems getting their preffered codecs on the Teliax web interface taking effect? I have two accounts, two separate yet similarly configured * servers. On one account the settings took right away - on another server I am getting no result. In fact, no matter what I change the settings to, only the old codecs are usable (otherwise * says it can't negotiate a codec). Teliax

We are looking to lose the TDM400P in favor of an ISDN-BRI solution. This should get rid of static on the line (at least any static generated by our half of the circuit), right? I am a total virgin to ISDN. I understand that we need two BRI circuits to provide four voice channels, and that the hardware to speak to the BRI circuits can be passive or active, with the active type being much more

Brent- There is no good way to say what changing the hardware and PSTN hookup will probably do for the echo problems. I'm not sure if you mentioned (lost in the past history of your post now) what sort of hardware you're using for PSTN connection now- TDMs, X100s, ATA's, etc- but that could also be a potential cause. I've heard tell of aftermarket X100s and certain ATA's

I have one use on our PBX who has been experiencing seemingly random disconnects. The user is on the same LAN as everyone else, using the same type of phone (79XX loaded with SIP firmware) as everyone else. He had some disconnects a few weeks ago, I suspected the phone, so I swapped his with mine. I have since not had issues with his old phone, however, he has had issues using mine. So, the

Dollars to donuts it is related to these two posts, but no one seems to know where or why it happens - this issue doesn't seem to be related to one specific piece of hardware: Post 1) ********************************************************* Anyone ever seen MeetMe cause * to crash? Specifically, it happens consistantly if someone begins to enter a conference and then decides to hangup while

I use IP Kall to forward my missed cell phone calls to. This way, if my phone is off, or out of a service area, calls will go to my * box. Concurrently, all incoming calls to my * box cause it to dial my local extensions at home, my extension at work, and my cell phone via NuFone. Problem: A loop can be created if my cell phone is not on. Say a call comes into my * box, it uses NuFone to call my

It does on my test phone. Is your tftp server available? -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of Brent Torrenga Sent: Monday, April 17, 2006 11:39 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] Sip Notify cisco-check-cfg - Does it still workwith 8.2? Has anyone else noticed that

>Brent, > >you mean, I could just remove the remark signs and number it 103, 104, >105, .... since it does not matter why it failed (busy, congestions) >(maybe for statistic purpose to add a log entry for the move to the next >provider). > >bye > >Ronald Yup. Take a look at the macro solution, too. I don't fully understand macros (I'm no programmer), and

Has anyone else noticed that notifying a 79[46]0 with cisco-check-cfg doesn't elicit any response from the phone using fw 8.2? Sincerely, Brent A. Torrenga brent.torrenga@torrenga.com Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 +1 219 836 8918 x325 Voice +1 219 836 1138 Facsimile www.torrenga.com

It doesn't seem as much broken as just annoying. I am holding off on upgrading until this resolves, but it doesn't seem to affect performance, anyways. BTW, some folks say that the server address only gets appended to the CID when a redirect or something comes about. Our experience here shows that the IP always gets appended. >Alexander Burke wrote: >> Just in case anyone here