similar to: T1, Rhino, & Nortel

Hello all, I have Asterisk 1.2.1 and a TE110P connected to a Nortel Meridian Option 81C system. The PRI line is currently setup as DMS100. Here are the relevant lines from zaptel.conf and zapata.conf: zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone = us zapata.conf: [channels] language=en context=from-internal musiconhold=default switchtype=dms100

Dear Gurus, i am facing some unknown problem here.. first, let me describe my case. my office is using a nortel merridian option 11c PBX. and it is connected to the provider thru a E1 card, which is working fine with no problem. my plan it to slot in a server with 2 TE11XP card to intercept the outgoing calls. Provider <--te11xp---> asterisk <---te11xp------> nortel merridian

picture. I know the firmware on the Nortel is old, so I'm guessing that libpri is sending something that the Nortel does not know how to handle. Is there a way to dumb down what libpri sends? From everything I've read PRI is an evolving standard - and older devices may struggle with newer extensions/developments. (This might be very handy for users trying to talk to old pbx's.) Is

Hi Guys, I am calling out 416-999-1111 on Channel 1 of PRI and then calling 416-999-2222 on Channel 2 of PRI. When the two channels are going to be ZAP native bridged, both channels hangup and CLI show PRI cause (16). Asterisk Verbose *(Channel 1 already connected to party)*: -- Requested transfer capability: 0x00 - SPEECH -- Called g0/4169992222 -- Zap/2-1 is proceeding passing it

Hi Guys, Full PRI installed in Canada with Sangoma A101DE and Asterisk 1.4.21.2, LibPRI 1.4.10. Placing a call into PRI and then transfering that call out to another number. Problem is that the call rings out but the moment the other party pickups both legs of the call are disconnected give Cause code 16.

handled. So....what do I do? Thanks, MD =1=================================================== !! Invalid Protocol Profile field 0x11 -- Accepting call from '2004000' to '111' on channel 0/23, span 1 -- Executing NoOp("Zap/23-1", "Incoming call from Meridian1") in new stack -- Executing NoOp("Zap/23-1", " From number: 2004000|

Told you it was too complex of an issue :-) I figured to do this in zapata.conf and all is fine now: transfer=no That was the magic two letter which was sending a request for RLT feature on the line. Set transfer to "no" and all worries gone. Thanks for the input everyone. -Bruce On Mon, Apr 12, 2010 at 10:10 PM, bruce bruce <bruceb444 at gmail.com> wrote: > Futher check

Hello List I'm trying to figure out what is wrong between my asterisk and my NEC 2400 pbx We have been trying to link them with a spare PA-24DTG from the NEC, I'm able to call an extension on the Asterisk, however the extension rings, and then immediatly hangs up I traced it back to the debug of the PRI on the Asterisk... I would appreciate if anyone could pin point what is wrong The

Hello, I have a problem, and I'm looking for you help. When I dial certain number my calls are getting dropped. I initiate the call, I hear IVR, then I am being transfered to operator, and then suddenly I get ISDN DISCONNECT message. I had this type of problem some time ago, and I thought it was a problem on the other end. But now this is a second time it occurred and I want an expert to

I have a T1 link from asterisk 1.2.23 (also tried with 1.4.13) to a Meridian Option 61C. Calls either way drop with error "Channel 0/23, span 1 got hangup, cause 100". Can anyone offer insight into the cause and solution/workaround? (I tried upgrading to Ast 1.4.13, and upgrading matching zaptel & libpri, put the problem is identical). For testing, I tried a call from the

hi all I have a PRI line which i have connected to my asterisk server. I am able to make calls to mobile no through my asterisk server, while i am not able to make calls to land line nos. This is strange. Where do u think the? problem is , is it from the service provider or? mis configuration of my asterisk. I am from India and using airtel pri lines. Below i am pasting you my configuration file

I have a working system with asterisk 1.4.26.2 libpri 1.4.1 and zaptel 1.4.12.1 With a digium TE205p. I am trying to update to libpri 1.4.10.2. When I do, incoming calls work but outgoing does not. When I do this I "rm /usr/lib/libpri*" then just install libpri-1.4.10.2 as normal. I then do a make clean in asterisk and make distclean ,then configure, make and make install. I do

I have a PRI E1 link between Asterisk 1.4.24 and Alcatel-Lucent OmniPCX Enterprise R9.0. As EuroISDN it works fine. However, I need to move to QSIG because of a firmware upgrade on the Alcatel PBX which doesn't support EuroISDN (please don't ask why). Besides, I've read somewhere that 2 B Channel Transfers "should" work with * 1.4, the latest 1.4 libpri and QSIG. So this

Hi all. I am searching for a way to send SMS via our E1 PRI line. We are in Portugal and I have seen some Internet/TV/Phone providers (ZON for those who know it) who install normal phones with SMS support in landline. So I just found a page from PT (Portugal Telecom) stating that the SMC number is either 12999 or 129990 (

Hey all, I am running a Asterisk 1.2.9.1 with Sangoma A101 card, newest firmware, configured with a help from Sangoma Tech Support, running fine. It is connected to a PRI circuit split from Cisco MC 3810, which in turn is connected to a Converged T from CTC Communications. While Asterisk works fine and I can call in/out on my BV account, I am only able to dial in through CTC. I have spent

So I reached the point where my PRI is accepting incoming calls, but I cannot dialout. I must be doing something stupid, but I can't figure it out. The Asterisk box is sitting between the Mitel and the phone company, and has PRI lines to each. Asterisk was built from CVS r1-0 Log for a call from mitel heading outbound: ------------------------- -- Accepting call from '' to

Hi all, I just configures my PRI and incoming calls are working fine but outside calling giving error PRI is BUSY :( any idea ? I have same setup on other box and that boxes works perfect. -- DAHDI/i1/6463279153-2 is proceeding passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is making progress passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is busy -- Hungup

I've a call center using IAX softphones provided by a third party. We've observed problems where the IAX phones seem unable to use our PRI trunks. A sample anonymized call is provided below with the PRI debug calls embedded. Any thoughts, comments or suggestions would be welcome. In anonymizing it, I preseved the format and number of digits sent. -- Accepting AUTHENTICATED

Hi all, I have to asterisk-1.0.9BRIstuffed-0.2.0n boxes each equipped with a TE410P. Box A is connected with pri1 to the PSTN. Box B is connected with pri1 (cpe) to the Box A at pri2 (net). Now I want Box B to dial out to the PSTN tunneled thru Box A and have it get all ISDN indications in case of call failure, eg. unallocated destination number etc. But currently Box B always gets only

Hello, I have an Asterisk system in the UK using ISDN service from BT. My problem is that the called number is always passed to the provider with the Type Of Number declared as ?national? despite pridialplan (and prilocaldialplan) is set to ?unknown?. My questions are: - How can I find out what the effective value is for the above two variables without actually making a call? (I have very