| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: buzz, distinctive, ring, same, set |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 4 ![]() | I have about a dozen M3904 sets in an office that has a "security buzzer" on the office door, which is kept locked most of the time (secure area). When someone wants in, they press a button at the door that calls a four digit extension which is on all of the 3904 sets. When answered, the answering set is connected to a two-way intercom at the door, and office personnel can then decide whether to open or not. The call-button/intercom unit is configured in the Meridian switch as a 500 type, and the DN it calls is programmed as MCR on various keys of the 3904s. I need the 3904s to ring regularly with the other DNs, but to “buzz” only once when the intercom button is pressed. If possible, I’d like it to buzz each time the button is pressed, just like a regular intercom. But as that probably isn’t possible, it at least needs to buzz every 5 or so seconds. Another problem with this is that I need to figure some way of not forwarding these calls to voice mail, while still forwarding regular calls. So far, I have programmed two test 3904s to CLS DRDA (LD 20). This gave two new settings of DNRO and DNRI under each DN key. Then changed the “FTC table 0” in LD 56 to: NDR2 BCS XTON 003 XCAD 003 Was: NDR2 BCS XTON 002 XCAD 002 Went back to LD 20, changed phone set “A” to DNRO 2. Now when I call test set “B” from test set “A”, there is a distinctive ring at “B”. Best I can tell from the books, is that the “003” value for XTON and XCAD under NDR2 selects sequence number 3 from a “NT8D17 TDS” table for the tone frequency and cadence. Problem is, I don’t know where to find this “NT8D17 TDS” table in order to modify an entry from a ring to a buzz, or if that is even possible. I’m not even sure I’m in the right neighborhood. And how do you make this repeat every 5 or so seconds? I am presented with a DRDA or DRDD in the CLS of a 3904 set for my test setup, but this option is not in the parameters for a 500 type. Can this be done with a 500? Finally, how do you make these calls not forward to voice mail, while all other calls do? I greatly appreciate any help!!! | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Junior Member
Location: France Rep Power: 6 ![]() | Can't tell for the buzz tone, but for not forwarding calls to VM you just need to create an extra phoneset with the same MCR nb as the 12 others and to specify it as MARP phoneset. Of course FDN and HUNT have to be blank. D. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Rep Power: 4 ![]() | Thanks for the reply. I was hoping there was a way to do that without having to dedicate a phone set and a TN. I realize that my post is kind of lengthy. Is that appropriate for this forum, or do you think I'm out of line? Thanks again, and I'll wait for more replies (hopefully) on the other issues... | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Senior Member
Location: Lou, KY Rep Power: 9 ![]() | Not too long of a post at all. As a matter of fact, it is a very well written scenario. Now, that being said, I don't know that what you want to accomplish is feasible with 3904s. Give the group some more time to chew on it and see what they come up with. This is a fairly creative bunch and they may have a trick or two for just this type of situation. It sounds like you are well on your way. Let's see what shakes out. rachelle | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Senior Member
Location: Lou, KY Rep Power: 9 ![]() | We use AI phones for this purpose. But, I'll take a stab at it: What is programmed at the door end of your signal path? Off the top of my head, I was thinking that you could program the door side to behave like a Group Call Key. Then on the M3904s you could program the GCKs to receive the door signal. That would give you a buzz for each depression of the key at the door. The TDS table I believe is something that we don't have access to. That would almost be a Nortel access issue. Any one else want to wade in on this teaser??? rlc | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member
Rep Power: 4 ![]() | The device at the door is a Viking Model C-1000B Door Entry and CCTV Camera Controller with a Viking W-1000 Handsfree Doorbox. Also, the PBX is a Nortel Meridian 1 Option 61C (sorry for not including that earlier). I read some about the group call feature (Rachelle's suggestion). Then modified my test setup to include an analog set and two M3904s. Went to LD 18 and entered: REQ NEW TYPE GRP CUST 0 GRNO 1 GRPC YES STOR STOR 01 5000 (Creates Group Call List #1, which calls extension 5000. 5000 is programmed as MCR on both M3904s [not as key 0] of test arrangement.) Then LD 57: REQ NEW TYPE FFC CUST 0 FFCT <cr> CEPT <cr> CODE GRPF GRPF 5555 GRCL 1 GRPF <cr> CODE <cr> (Creates Flexible Feature Code [FFC] of "Group Call". Access number for code is "5555", and it calls the number stored in Group Call List #1 [5000], created in LD 18 above.) So, when 5555 is dialed from the analog set, both M3904s ring at 5000, and the call is NOT forwarded to VM. I think this solves the problem of getting it to not forward to VM, but I haven't had the chance to test it thoroughly yet. That also started a new problem (it's always something!) of CPND for a phone originating a group call. It now just says "-01" for the caller. Any suggestions? More about this later; it's time to go home! | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Two phones with same DNs - ring on one only | twscrb | Meridian Systems | 2 | 10-29-2003 01:06 PM |
| MCR and ring style | daved | Meridian Systems | 12 | 05-05-2003 03:00 PM |