| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| 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: busy, fast, prefix |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #2 (permalink) | ||||||||
| Senior Member
Location: Lou, KY Rep Power: 9 ![]() | Question re: digits dialed Have you verified that this is a valid prefix? Are you sure that it is in the NXX of the correct access code (AC1/AC2)? Are you sure you have a valid number to test with? rlc __________________ No matter where you go, there is the Ladies Love Marty Fan Club. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Location: Puerto Rico Rep Power: 6 ![]() | Telnet Port for Merdian1 Yes it is a valid prefix and it is assigned as AC1, RLI 1 and also tried 0 which are the two that we are using...let me try AC2 to see if it works. Yes we have try calling from out of the SL1 and it rings. and yes it is an NXX. let me know anything else that I could do at my end... Thanks | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Senior Member
Location: Chicago -- CENTER OF THE UNIVERSE Rep Power: 10 ![]() | Off Site Call Forwarding Policy When are you getting the reorder, as soon as you dial 641 or after all 7 digits are dialed? Can you post the nxx programming for 641 as well as any working nxx? Have you tried to trace the call to determine if you are leaving the switch or not? Is this on a pri circuit? If yes check out what your d-channels say that your outpulsing, presuming you are getting out of your switch. This reorder occurs on multiple phones not just 1, correct? Post back and we can go from there. Jack __________________ Dogs rollover Phones hunt | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Junior Member
Location: Puerto Rico Rep Power: 6 ![]() | international calling through BARS I am getting it after all 7 digits are dialed... nxx 641 rli 1 or 0 sdrr none itei none same as all other nxx... to dial out npa is npa 1787 rli 4 sdrr none itei none also for 787 for local calls its not leaving the switch since it has to go thru an SL100....if I dial the number from the Sl100 it works good but dialing from the SL1 it's the only prefix that is not going out. I tried diailing from other phones in the sl1 and same results. It is not on a PRI Circuit it goes thru a regular outgoing T1 | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Junior Member
Location: Chlt-NC Rep Power: 6 ![]() | international calling through BARS Do you have access to the SL100? If so do this at the CI level TRAVER TR <trunk group name> <digits dialed> B where: trunk group name is the name of the tie line trunk group digits dialed is the digit string as seen from the M1 (1787641xxxx) Do the traver with both the "broke" prefix" and a good prefix and see where the call gets blocked. TRAVER is the resident "Translations Verification" tool. Heres an example: TRAVER TR Some_M1_Tie 813155551212 b TL2UPTOWN IBNT2 0 ELO NCRT SL100 0 LIDL 228 N ANSDISC 0 Y N N N N Y Y 0 228 N 0 0 0 0 N N N N N N N N N NATL $ TABLE CUSTSTN TUPLE NOT FOUND TABLE OFCVAR AIN_OFFICE_TRIGGRP NIL TABLE NCOS SL100 228 0 0 NCO228 ( XLAS PTN228 FET1 DGTC) ( OCTXLA OCT1)$ TABLE CUSTHEAD: CUSTGRP, PRELIMXLA, CUSTXLA, FEATXLA, VACTRMT, AND DIGCOL SL100 NXLA CTN1 FET1 0 DGTC TABLE DIGCOL DGTC 8 POTS Y TABLE IBNXLA: XLANAME PTN228 TUPLE NOT FOUND Default is to go to next XLA name. CUST PRELIM XLA name is NIL. Go to next XLA name. TABLE IBNXLA: XLANAME CTN1 CTN1 813 NET N Y 1 Y NDGT Y N DOD N 20 081_SP0_11 NLCA_NILLA_0 NONE $ TABLE DIGCOL NDGT specified: digits collected individually TABLE LINEATTR 20 IBN NONE NT 0 0 NILSFC 0 NIL NIL 00 081_SP0_11 NLCA_NILLA_0 $ LCABILL OFF - BILLING DONE ON BASIS OF CALLTYPE TABLE XLAPLAN 081_SP0_11 CSSC 081 SP0 AMRX N $ $ TABLE RATEAREA NLCA_NILLA_0 NLCA NIL NILLATA $ TABLE STDPRTCT SP0 ( 1) ( 0) 1 . SUBTABLE STDPRT WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO DOCUMENTATION. . 13 19 N DD 1 NA . SUBTABLE AMAPRT . KEY NOT FOUND . DEFAULT VALUE IS: NONE OVRNONE N TABLE HNPACONT 081 Y 998 15 ( 34) ( 1) ( 0) ( 0) 2 $ . SUBTABLE HNPACODE . 3154 315555 FRTE 7 . SUBTABLE RTEREF . 7 T IBNRTE 120 . . TABLE IBNRTE . . 120 ISA N N N SPRINT N PUB NONE 0 N 0 . . . TABLE TRKGRP . . . SPRINT IBNT2 0 ELO NCRT SL100 0 ASEQ 225 N ANSDISC 0 Y N N N N N Y 0 225 N 0 0 0 . . . 0 N N N N N N N N N NATL (LTID SPRINT 1) $ . . . TABLE LTCALLS . . . SPRINT 1 PUB XLAIBN 4 704_SP2_4 NLCA_NILLA_0 SL100 0 225 $ . . S N N N N MCI_VNET2 . . S N N N N MCI_VNET1 . . S N N N N ATTNET . . N N N N N MCI_VNET3 1 . . . TABLE DIGMAN . . . 1 (INC 1) . . . EXIT TABLE DIGMAN . . EXIT TABLE IBNRTE . EXIT TABLE RTEREF EXIT TABLE HNPACONT LNP00100 SOC Option is IDLE. LNP Info: Called DN is not resident. LNP Info: HNPA results are used. TABLE CLSVSCRC 081 CSSC DD 2 N NONE ( 1) . SUBTABLE CLSVSCR . KEY NOT FOUND AIN Info Collected TDP: no subscribed trigger. AIN Info Analyzed TDP: no subscribed trigger. +++ TRAVER: SUCCESSFUL CALL TRACE +++ DIGIT TRANSLATION ROUTES 1 SPRINT N CDN E164 NA 3155551212 NIL_NSF BC SPEECH Outpulsing on this route is modified by the following options: (DNIS) 2 MCI_VNET2 N CDN E164 NA 3155551212 NIL_NSF BC SPEECH Outpulsing on this route is modified by the following options: (DNIS) 3 MCI_VNET1 N CDN E164 NA 3155551212 NIL_NSF BC SPEECH Outpulsing on this route is modified by the following options: (DNIS) 4 ATTNET 3155551212 ST 5 MCI_VNET3 13155551212 TREATMENT ROUTES. TREATMENT IS: GNCT 1 T120 +++ TRAVER: SUCCESSFUL CALL TRACE +++ | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member
Location: Puerto Rico Rep Power: 6 ![]() | Call Routing (Internal VS. External) Everything on the SL100 looks good and it is programed...I could dial out from the SL100 prefix 641 but coming out of the SL1 negative....all other prefix are working great except 641, what else can I check to make this work. :casstet: | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member
Location: Chlt-NC Rep Power: 6 ![]() | Mat to OTM 2.0 Premium Just because you can dial it from the SL100 does not mean you can translate the call properly from the M1. The NCOS on the trunk group may be using a different prettanslation than your stations do. It can be any number of things, your trunks can be using a different STS in HNPACONT, and the prefix may not be included there. Do a traver like I suggested and see what the results are. Does the traver show the call going out a route or a treatment such as T120? | ||||||||
| | |
![]() |
| 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 |
| Fast Busy when 6 are in IVR | StarFury | Contact Center Symposium and ACD | 3 | 09-26-2006 03:47 PM |
| Extension Fast Busy | 612moto | Meridian Systems | 24 | 10-06-2004 11:15 AM |
| DAGA BOUND | Java_Bob | Off Topic - Humor/Jokes | 5 | 09-28-2004 08:52 PM |
| Am I being hacked? | cliffzig | Meridian Systems | 8 | 09-10-2004 08:51 AM |
| Urgent - incoming number ringing fast busy | sneexy69 | Meridian Systems | 5 | 10-28-2003 02:48 PM |