![]() | |
| |||||||||||||||
| |||||||||||||||
| 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: nt8d14, problem, problemran, utrk, voltage |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Option 61c/release 3/interalia/Meridian Mail/No symposium I'm having trouble again with my Interalia digital announcers I use for my RAN routes... They play for about a minute then return a fast busy intercept after the dreaded err220... Yes I've checked the grounding every way I know how and it seems to be ok. Interalia tells me that I should have 24vdc or very close to that on the cp lead of the NT8D14 trunk card... I'm reading 19 vdc. I've tried different card vintage, AJ, BB, BA on different shelves and I still only get 19 vdc. Do you know the specs on this card or where I can find them? How accurate should the card output be? If the specs say 24vdc should it be 24vdc? Any ideas? thanks -ck | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | thanks... the interalia tech I called told me 24... I'm thinking 19 if fine also... I just don't know what the heck is wrong... I out my route and trunk and rebuild them. I can dial the RAN via the ACOD from my phone without any problem... but after a minute or so it ERR220's out and then I can't access it... I get a fast busy intercept. When I to a RAN c r Test in LD 32 I get err trk041 - "The RAN, MUS or AWK device specified for customer c and route r is not operable." - I just don't know... ck | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Hello, Here is what I have found to be my experience, The 24VDC is what should be present on the CP (3rd) lead of the Trunk Card, this voltage should be present even with the Interalia disconnected. If you have the Interalia configured in the Continuous Play (CP-NO) mode the announcer is designed to short that voltage to ground (this is why the grounding is so important) every time the message starts over. This signal (short) is what "tells" the PBX that the Interalia is about to play the message and a caller waiting for that message should be connected at that point. If the PBX does not see this short in a certain period of time it errors out the port (Error 220) A way of verifying if the Interalia is operating properly is to: 1) Monitor this voltage - The CP leads of the Interalia should momentarily close (for 250ms) at the start of the recorded message. If, for example, the message was ten seconds long you should see the voltage drop every ten seconds. 2) You could also verify the Interalia's operation with the PBX out of the picture - Connect your meter across the CP leads of the Interalia, the CP leads should provide a momentary closure (short) every time the message is about to start (again, every ten seconds). Ultimately (once you verify the operation of the Interalia), the questions is how much voltage should be present on the CP lead of the trunk card? My experience has been that there should be almost 24VDC. The 20 VDC Min that PP is referring to is when a PBX is configured for E&M signaling and the Interalia is triggered to play a greeting. In this case the Interalia would also need to be configured for E&M signaling (either Pulse or Level Start) - Applying 20 VDC Min to the Start Leads of the Interalia will activate the announcement in the Interalia. | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Junior Member ![]()
Location: Missouri Rep Power: 8 ![]() | How long is the message on the Interalia? I found something on the Nortel website that says the Audicron interface requires a CP every 64 seconds. If it doesn't hear it, the ERR220 is generated. Also, another note says someone had a problem when the Interalia ground wasn't the same as the system ground. | ||||||||
| | |
| | #7 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Interalia problem. Thanks all for the replies... I am set up as AUD, DDL, CP and the message length is under 10 seconds for testing purposes... Interaliatech, I've monitored the message with my test set and verified that the voltage does drop during the short. I did this by putting on meter lead on the cp lead org/wht and the other to ground... Now "to ground" is what I'm worried about... I've tried it using the ground lead Grn/Wht, I tried grounding to a BellSouth 21x ground bus, to the main breaker box and I even took cross connect wire to the base of the pedestal where the switch is grounded and the result is the same... I've tested from the Grn/Whit to the breaker box cabinet and read 5 ohms which I believe is a standard for a good ground... nothing changes... The voltage, 19 vdc, is the same on different cards and IPE shelves... I'm using a NT8d14 BB card... is this and XUT or the updated EXUT card? You stated, "You could also verify the Interalia's operation with the PBX out of the picture - Connect your meter across the CP leads of the Interalia, the CP leads should provide a momentary closure (short) every time the message is about to start (again, every ten seconds)." When you say, connect your meter across the CP LEADS, what do you mean? Each channel has one CP lead and one GND. The GND is looped to the other channels... So when you say "across" the CP leads... ??? my dip switch settings have not change... they are off off off (123) on on off on (4567) which is continuous play. Attached is my RDB and Trunk. I need to know if I'm using an XUT or EXUT card... I think EXUT... The TIMP is different for each. Just found out that XUT only supports continuous play... I have a vintage BB which is what interalia calls for so I relatively sure I have an EXUT card. I also get this when I test the RAN Route... TRK0041 c r "The RAN, MUS or AWK device specified for customer c and route r is not operable." Severity: Minor I think the problem is my switch is not seeing the short to ground... I see it at the CP lead... That's why it will work for about a minute then time out with the err 220... the switch never sees all the shorts within that minute. The question is, why is my switch not seeing the short!? I think the problem is my switch is not seeing the short to ground... I see it at the CP lead... That's why it will work for about a minute then time out with the err 220... the switch never sees all the shorts within that minute. The question is, why is my switch not seeing the short!? RDB: TYPE RDB CUST 00 ROUT 10 DES TEST TKTP RAN NPID_TBL_NUM 0 VTRK NO RTYP AUD GRD IDLE REP 1 POST DIS RANH STRT DDL WAIT RGB BDCT NO ASUP YES ACOD 712 TARG 01 CDR NO MUS NO RACD NO TTBL 0 OHTD NO ALRM NO SGRP 0 AACR NO EXUT Trunk: DES TEST TN 008 0 00 00 TYPE RAN CUST 0 XTRK EXUT TIMP 600 BIMP 600 AUTO_BIMP NO RTMB 10 1 DATE 31 JAN 2007 XUT Trunk: DES TST TN 008 0 00 00 TYPE RAN CUST 0 XTRK XUT TIMP 1200 BIMP 600 RTMB 10 1 DATE 1 FEB 2007 | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Hi fatmoses, The CP Leads that I am referring to are (for line one) the Org/Wht pin 2 - This is the CP-C (Common) lead and the Grn/Wht pin 3 - This is the CP-NO (Normally Open) of the Interalia - They provide the Control Pulse or Short (in reality, they are two legs of an internal relay). When connected to the PBX the Org/Wht(pin 2) is connected to the third lead of the Trunk Card and the Grn/Wht(pin3) is connected to ground. I believe you have this wired correctly. What I was saying was that by connecting your meter across these two leads you should be able to verify whether or not the Interalia is providing the closure needed, however, as you said you are seeing the drop in voltage which tells me the Interalia is connected properly. One item in the RDB that "may" be an issue is the setting for TARG 01. Would it be possible to change this? Try 0 (anything but one) - You will need to reset the card after making the change. I believe the other setting are fine. I will check back and hope for good luck! | ||||||||
| | |
| | #10 (permalink) | ||||||||
| Junior Member ![]()
Location: Missouri Rep Power: 8 ![]() | Can you try this: Disconnect the XUT CP lead from the Interalia, then run a wire connected to the system ground. Touch this to the CP lead on the MDF during the RAN playback and see if the system connects the call to the RAN (instead of letting the Interalia attempt to close the CP lead to ground). This would at least let you know if you have a wiring problem between the MDF and the Interalia. | ||||||||
| | |
![]() |
| 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 |
| Call Register Problem: Problem with Dropped Calls on Tansfer | rixride | Meridian Systems | 4 | October 31st, 2006 10:05 AM |
| Voltage and Analog questions | hsantos | Meridian Systems | 12 | August 11th, 2005 02:45 PM |
| Need Voltage limits | Rachelle | Meridian Systems | 3 | February 2nd, 2005 10:14 AM |
| Analog port voltage survey | freddog | Technology | 6 | September 30th, 2003 02:21 PM |
| Message Waiting Voltage | PD | Meridian Systems | 1 | April 9th, 2003 11:33 AM |