similar to: MeetMe - Causes * to crash :/

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

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

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

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

Hi Brent > 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

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

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.

Is it possible to dial more than one extension with a different CID to each extension? I'm thinking macros might be needed, but I don't have a good handle on macros. Is it possible? Any hints? BTW - this would be used for showing an internal extension to one phone and a PSTN accessible number to another phone. Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road

I am thinking of turning on the NAT option in our Cisco phones (and the corresponding sip.conf modification) to allow the phones to be taken outside the LAN. Can anyone think of any reason not to just always turn on the NAT enabled option? I can't think of a reason not to always operate these phones with this enabled, since it would likely allow them to be taken outside our LAN and used.

Hola, What would a valid regexp in Asterisk be to identify a NANP number, i.e., NXXNXXXXXX? Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 tel:+1 219 836 8918 x325 fax:+1 219 836 1138 email:brent.torrenga at torrenga.com web:www.torrenga.com

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

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

Dear list (and more specifically Bret), I am getting one-way (inbound only) audio when trying to place a SIP call via voip.trxtel.com (i.e. 18005558355@voip.trxtel.com). The Cli spits out "== Forcing Marker bit, because SSRC has changed" 5 times after atempting a native bridge. I realize this is most certainly a NAT issue, the * server is behind one. Sip.conf has externip=, and

I think A@Home allows a user to search a directory by either first OR last name, right? I don't know for sure since I don't run A@Home. I would like to offer that functionality in my system - and I'd have done it by now if there was a prompt where Allison asks "press 1 to search by first name, press 2 to search by last name". But I don't think that prompt exists. Can

>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 =>

Out internet connection was out this morning. It seems that the SIP extensions on our LAN were affected. Behavior like: Call comes in over POTS to a TDM400P, there is a delay then before the Cisco 79[46]0's start to ring. If we were lucky enough to get a call through, then we could not transfer the call, or place the call on hold, or park the call. Outbound calls seemed to have a delay

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

Can someone explain how to use groups? I can't seem to wrap myself around this, though I know it is something simple. I have 3 zap lines, and when placing an outgoing call, would like to 1) use a zap line if and only if 1 or fewer zap lines are being used at the time, and 2) if more than 1 zap lines are in use then to go ahead and use VOIP to place the call. Also, is there a difference

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