| |||||||||
 |
| ||||||||
| |||||||||||||||
| |||||||||||||||
| 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: cpnd, odd, problem |
 |
| | LinkBack | Thread Tools | Display Modes |
 11-10-2003, 06:23 PM | #1 (permalink) | ||||||||
| Junior Member
Location: Oregon Rep Power: 0  Country:  | Hello all - long time reader, first time poster... I am a PBX rookie looking into an odd problem. Our site consists of a 61c hub with 11Cs hanging off of it with PRI TIE lines. At a particular site, CPND works as intended for calls within that PBX. If a call is made to a DN outside that PBX, but within our network, CPND doesn't work (i.e. no name is displayed on the caller's phone). I'm not sure what configuration information would be useful so I haven't included any. Please let me know what would be useful for debugging and I'll be happy to post it. Thanks in advance for any replies. -mtw | ||||||||
 |   |
| 11-10-2003, 07:38 PM | #3 (permalink) | |||||||||
| Junior Member
Location: Oregon Rep Power: 0 Country: | Quote:
These are T-1 PRIs, and yes there is a D-channel to the remote site. -mtw | |||||||||
| | |
| 11-11-2003, 02:21 PM | #4 (permalink) | ||||||||
| Junior Member 
Location: New Zealand Rep Power: 7 | 0x32 mod ics rel1 t1 OK. Assuming that this is a Meridian to Meridian PBX tie, the d-ch needs to be set up as follows. ADAN DCH 12 CTYP MSDL DNUM 11 PORT 3 DES Waitakere_Lp_19 USR PRI DCHL 19 OTBF 16 PARM RS422 DTE DRAT 64KC CLOK EXT NASA YES IFC SL1 SIDE NET SEMT 1 CNEG 1 RLS ID 25 RCAP ND2 NCT MSDL MBGA NO OVLR NO OVLS NO T200 3 T203 10 N200 3 N201 260 K 7 As you describe this as a CPND problem I would check that the RCAP setting ND@ is set at both ends. ND2 = network name display method 2. ND2 is what I always use & it's been so long since I chose that I can't remember what the reasons were | ||||||||
| | |
| 11-12-2003, 01:23 PM | #5 (permalink) | ||||||||
| Junior Member
Location: Oregon Rep Power: 0 Country: | ah ha! Bruce, thanks a lot. It appears that out of the 14 sites I have, this is the only one that is configured differently. Most sites have: RCAP TAT ND3 While the site that doesn't work has: RCAP ND2 NCT TAT I'll change the RCAP entry for this PRI and we'll see if it works. | ||||||||
| | |
| 11-19-2003, 10:35 AM | #7 (permalink) | ||||||||
| Senior Member  Fletch is Nortel E911 PLM
Location: NORTEL - NJ Rep Power: 7 Gender:  Country:   | RCAP NCT is used for Network Call Trace and should not have affected your situation. Chances are that the MSDL card for the DCH was slightly hosed and when you brought it down to make the RCAP change, the problem cleared. Fletch | ||||||||
| | |
| 11-20-2003, 05:48 PM | #8 (permalink) | |||||||||
| Junior Member
Location: Oregon Rep Power: 0 Country: | Reply Quote:
| |||||||||
| | |
| 11-24-2003, 09:32 AM | #9 (permalink) | ||||||||
| Senior Member Fletch is Nortel E911 PLM
Location: NORTEL - NJ Rep Power: 7 Gender: Country: | Opps! I missed the ND2/ND3 part! That was your problem. ND2 is fine if you do an MCDN network, and NEVER plan to implement Q.Sig on your PRI's. If you plan on doing Q.Sig in the future, all of you RCAPS should be set to ND3. This allows CPND tandeming between MCDN and Q.Sig. It needs to be on in your entire network to work correctly. Fletch | ||||||||
| | |
|
| 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 |
| Telco problem or not? | ETITech | BCM and Norstar | 7 | 05-01-2006 08:16 AM |
| Really Strange MICS/AA/Voice Mail problem | lgherb | BCM and Norstar | 5 | 04-06-2006 09:30 AM |
| Callpilot Apllication Problem | sneexy69 | Meridian Systems | 2 | 11-22-2003 12:23 PM |
Linear Mode
