similar to: Re: No Caller Name sent from Asterisk over National or DMS100?

All good information, thanks. However this is private network between Asterisk and a Norstar MICS about six feet away. So I'm holding both ends of the link. :-) > -----Original Message----- > From: David Troy [mailto:dave@popvox.com] > Sent: September 16, 2004 4:57 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] No Caller Name

I have a PRI link up and running between Asterisk and a Nortel Norstar MICS v4.1 . I'm having a problem getting the textual Caller Name across the link from Ast to Ns, however numeric Caller ID arrives and displays fine. From Ns to Ast both elements come through fine. I'm forcing dummy values for testing using: exten => s,1,SetCIDName(Test) exten => s,2,SetCallerID(1234561234)

Hello, Quick Diagram: Telco-PRI -> Asterisk <- Norstar PRI -> Norstar PBX (DMS100) (TE405P) (DMS100) | | V Cisco 7960G (SIP) I'm trying to change the Origination Number on my outgoing PRI, and running into a weird problem. If I make a call from a SIP extension off asterisk using the following context:

We have a DMS100 that does not have PRI. So we're using a channelized T1 using WU-LAW, ESF and B8ZS coming from the DMS100 that's plugged into a Tormenta2 Quad T1 Card on my Asterisk Box running Debian 3.01(woody) with Kernel 2.4.22. The Link is up but according to the DMS100, Channel_1 goes into RMB (Remote Manual Block) and Channel_2 goes into LO (Lock Out). I've been through all

Hi, I dropped an asterisk server with a TE405P between a Norstar Meridian PBX and it's PRI PSTN connection. Everything seemed to work fine using a pass-thru-type dialplan configuration... except now we've realised that outbound calls to celphones get dropped upon connect, but not on every call (almost always the first try, but not the second). All other calls to non-celphones had no

i cannot see caller ID of the call originated from outside zap channel. i hv configured both zapata.conf and extensions.conf. i m right now in india i think asterisk only supports Bellcore enable caller ID. so is it the same bug of BT caller ID problem in UK? or it is the bug of my asterisk configuration? i hv enabled callerID from my TELCO. -------------- next part -------------- An HTML

I have not been able to get two B-channel transfer to work on DMS100 PRI. I consistently get the following errors: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ROSE RETURN ERROR: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: OPERATION: RLT_OPERATION_IND [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ERROR: RLT Not Allowed I have tried on two

so i have been running v1-0 on all of my test boxes for about a month now testing iax/sip/res_xxx. I decided to put it into production so I updated a box that was running 0.9.? that had been working perfectly for months and low and behold the inbound line from telco now intermittantly doesn't clear and none of the other channels can dial out on that line. I have tested the line in this

To All; My current issues is a 5 second delay for call that is being transferred from the Norstar units to the Asterisk servers VIA a PRI. Is their anything that can be done to speed up the transfer on the Norstar. Below is my current phone config. < Norstar1 >----PRI----< Asterisk-1 >----IP-WAN----< Asterisk-2 >---PRI---< Norstar2> The Norstars are MICS 0x32 4.1

-----Original Message----- My question concern outgoing calls. How can I configure my extensions.conf to get a PSTN line on my TDM04B card in the following order : first trying on the channel 4 then if 4 is busy then switch to 3 if 3 is busy then switch to 2 and if 2 is busy then say there's no more line available. I don't want to dial on the first channel as it's my main number

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

The last post I saw regarding this was June 2003 (before my time with *, I started in September): http://lists.digium.com/pipermail/asterisk-users/2003-June/013324.html Is there any support for Q.SIG in * at all? The Norstar MICS uses a MCDN (Meridian Customer Defined Network) key to enable the "SL1" protocol which from everything I've been reading is just Q.SIG. This protocol

-----Original Message----- <snip> Is this possible with asterisk? Anyone have a sample dialplan? -other than the problem outlined below I would try something like S,1,wait(20) S,2,voicemail(uwhatever) S,3,hangup That should ignore the call for 20 seconds and then leave a message in the unavailable greeting for 'whatever' then hangup That leaves another problem -

Hi, Is it possible to set the pridialplan (or prilocaldialplan) on a call-by-call basis, or for a particular PRI channel-group? >From my experimentation so far, it appears to me that the pridialplan and prilocaldialplan are global in zapata.conf, unlike other options such as switchtype, signalling, and context. I currently have two PRIs from different providers (and different

I am currently working on an Asterisk test system, and will be presenting a demo to the Board of Directors tomorrow night. I want to make sure I have all of my ducks in a row. The Asterisk system will be used to replace a Norstar MICS. The location has two PRI's coming in, with a few hundred DIDs. I know how to make * use the DIDs incoming, and I know how Nortel uses the DIDs. Now for the

Hi folks -- For those of us trying to develop interactive web-based Asterisk applications, it can be a challenge getting Asterisk integrated in a cgi/mod_perl/php environment. The load associated with making multiple connections to asterisk via the manager port, having to teach our applications to parse "manager-ese", and a variety of other factors have all pointed to the need for

Hi, Looking through the source code, I see two functions in the 'libpri' code for message-waiting: pri_mwi_activate, and pri_mwi_deactivate, but they are not used by anything anywhere. Is there a sample application somewhere which makes use of these functions? I believe that the ISDN MWI is used when a Norstar MICS has an external voicemail provider. I don't know exactly how this

Out of the blue i started receiving the following error on my PRI line which connects my asterisk server to a Norstar 0x32 key system. The asterisk zaptel.conf file was configure as follows and this config worked for 6 months until friday. Nothing was changed on either system prior to friday. here is teh zaptel.conf span=1,0,0,esf,b8zs bchan=1-23 dchan=24 span=2,0,0,esf,b8zs bchan=25-47 dchan=48

I have been investigating more tight integration between * and the Nortel MICS... it appears that it is at least theoretically possible to have * store voicemail and log which stations call where. Both require a T1 card. The T1 card requires either a clocking module or the 6-port fiber module to provide T1 timing. Naturally a T100P or TE405P is required on the * side. To log which

Unfortunatly no on both counts. The arrangement right now has: PSTN Trunks & Stations <-> Nortel Norstar#1 <-CT1-> Asterisk#1 <-IAX2-> Asterisk#2 <-CT1-> Nortel Nortstar#2 <-> Stations The Asterisk boxes provide Voicemail to their sites Norstars and intersite calls over IAX. Local Voicemail works flawlessly at each site but there have been reports of PSTN calls