Welcome, Guest. Please Login or Register
Telcom Pro's
 
  HomeHelpSearchLoginRegister Nortel MetaSwitch  
 
 
Page Index Toggle Pages: 1
Send Topic Print
non-pri diod to pbx table configs (Read 146 times)
Jul 29th, 2010 at 10:42am

tsands   Offline
Junior Member
Translations Technician
I Love Telcom!!
iowa

Posts: 6
**
 
Working on turning up a new diod (non-pri) to a customer PBX. The customer requested DTMF WK. The grptype is PX in table trkgrp. I'm using DT WK in table trksgrp. Customer able to complete outbond calls. But inbound calls go to dead air. On just one of the four Ts. Customer can take pbx to another location ( I don't service at that location) and carriers come right in service. Passes traffic in both directions. Ran to loops on nius and runs clean all zeros. All four Ts run clean.The other three carriers won't come into service. The customer request b8zs esf. We have checked all the muxs line coding.
 
IP Logged
 
Reply #1 - Jul 29th, 2010 at 10:56am

Paul   Offline
Site Administrator
Switch Technician
Southern Maine

Posts: 237
*****
 
Tsands,

Your write up is a little difficult to follow but I understand that there are 4 T-1's.

Some questions:
Do the carriers for all 4 T-1 go "In-Service" on the DMS?

If not has a field technician been on-site and used a hand held T-1 tester to confirm polarity?  Can the technician get the carrier to come up to his tester?

If he can can you verify how many DNIS digits the customer wants to see?  All 10 or something less and does your subscriber config match?

If you can, post the table entries for your customer so we can review them and make observations.
 
IP Logged
 
Reply #2 - Jul 29th, 2010 at 11:19am

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
Check table ltcpsinv if the T1s are on a DTC/DTCI or table mnhscarr if the T1s are on an spm to insure the T1s are set to B8ZS/ESF at the DMS.

I, also, am a little confused by your explanation, but answering Paul's question shoould provide more insight.
 
IP Logged
 
Reply #3 - Jul 29th, 2010 at 12:55pm

tsands   Offline
Junior Member
Translations Technician
I Love Telcom!!
iowa

Posts: 6
**
 
I have four T1s. In two trunk groups (tmone dtc 27-2,27-4 and tmoneld dtc 25-5,20-16). To the same pbx. Same datafill in trkgrp,trksgrp,and ltcpsinv.

All four carriers T1s will come into service on rts. But will not recover on their own from sysb.

I'm now getting reorder on outbound and inbound calls on all four T1s.

pos tmone
           TMONE
       PX              0
                          ELO     NCRT 2W        MI       MIDL Y     COSD
LOC1 605 605  LCL NONE    TSPS NLCA N                 N    71 NIL
6052421600 NODIALTN N Y      INS Y   LATA1     N
                                                                           $
>quit
CI:
>table trksgrp
TABLE: TRKSGRP
>pos tmone 0
           TMONE 0    DS1SIG
    STD
2W DT WK N 10 10 DT WK 7 0 Y NO NO N N N M 135 UNEQ $
>quoit^H^H^H

[132D
[005C
[132D
[004C
[132D
[003CUndefined command "QUOIT".
>quit
CI:
>table ltcpsinv
TABLE: LTCPSINV
>pos dtc 27
       DTC  27
          N (0 DS1 DTCB8ZS N) (1 DS1 DTCB8ZS N) (2 DS1 DTCB8ZS N)
          (3 DS1 DTCB8ZS N) (4 DS1 DTCB8ZS N) (5 DS1 DTCB8ZS N)
          (6 DS1 DTCB8ZS N) (7 DS1 DTCB8ZS N) (8 DS1 DTCB8ZS N)
          (9 DS1 DTCB8ZS N) (10 DS1 DTCAB N) (11 DS1 DTCAB N)
          (12 DS1 DTCAB N) (13 DS1 DTCAB N) (14 DS1 DTCB8ZS N)
          (15 DS1 DTCB8ZS N) (16 DS1 DTCB8ZS N) (17 DS1 DTCB8ZS N)
          (18 DS1 DTCB8ZS N) (19 DS1 DTCB8ZS N) $
>pos dtc 25
       DTC  25
          N (0 DS1 DTCB8ZS N) (1 DS1 DTCB8ZS N) (2 DS1 DTCB8ZS N)
          (3 DS1 DTCB8ZS N) (4 DS1 DTCB8ZS N) (5 DS1 DTCB8ZS N)
          (6 DS1 DTCB8ZS N) (7 DS1 DTCAB N) (8 DS1 DTCB8ZS N)
          (9 DS1 DTCB8ZS N) (10 DS1 DTCB8ZS N) (11 DS1 DTCB8ZS N)
          (12 DS1 DTCB8ZS N) (13 DS1 DTCB8ZS N) (14 DS1 DTCAB N)
          (15 DS1 DTCB8ZS N) (16 DS1 DTCAB N) (17 DS1 DTCB8ZS N)
          (18 DS1 DTCB8ZS N) (19 DS1 DTCB8ZS N) $
>table carrmtc
TABLE: CARRMTC
>lis 10
TOP
CSPMTYPE          TMPLTNM RTSML RTSOL                                   ATTR
----------------------------------------------------------------------------
     DCM          DEFAULT   255   255       DS1 NT2X35AB   17  511    4  255
     DTC          DEFAULT   255   255 DS1 NT6X50AA MU_LAW SF ZCS BPV NILDL N
                                      250 1000 50 50 150 1000 3 6 864 100 17
                                      511 4 255
     DTC            DTCAB   255   255 DS1 NT6X50AB MU_LAW SF ZCS BPV NILDL N
                                      250 1000 50 50 150 1000 3 6 864 100 17
                                      511 4 255
     DTC          DTCB8ZS   255   255 DS1 NT6X50AB MU_LAW ESF B8ZS BPV NILDL
                                      N 250 1000 50 50 150 1000 3 6 864 100
                                      17 511 4 255
     DTC           DTCESF   255   255 DS1 NT6X50AB MU_LAW ESF ZCS BPV NILDL
                                      N 250 1000 50 50 150 1000 3 6 864 100
                                      17 511 4 255
     DTC          DTCSFB8   255   255 DS1 NT6X50AB MU_LAW SF B8ZS BPV NILDL
                                      N 250 1000 50 50 150 1000 3 6 864 100
                                      17 511 4 255
     LTC          DEFAULT   255   255 DS1 NT6X50AA MU_LAW SF ZCS BPV NILDL N
                                      250 1000 50 50 150 1000 3 6 864 100 17
                                      511 4 255
     LTC              ESF   255   255 DS1 NT6X50AB MU_LAW ESF ZCS BPV NILDL
                                      N 250 1000 50 50 150 1000 3 6 864 100
                                      17 511 4 255
     LTC               SF   255   255 DS1 NT6X50AB MU_LAW SF ZCS BPV NILDL N
                                      250 1000 50 50 150 1000 3 6 864 100 17
                                      511 4 255
     LTC          LTCESB8   255   255 DS1 NT6X50AB MU_LAW ESF B8ZS BPV NILDL
                                      N 250 1000 50 50 150 1000 3 6 864 100
                                      17 511 4 255
>quit
TABLE: LTCPSINV
>quit
CI:
>table clli
TABLE: CLLI
>pos tmone
           TMONE   493       96                        TMONE_PBX
>pos tmoneld
         TMONELD   494       48                     TMONE_PBX_LD
>table trkgrp
TABLE: TRKGRP
>pos tmoneld
         TMONELD
       PX              0
                        NPDGP     NCRT 2W        MI       MIDL Y     COSD
OPER 605 605  LCL NONE    TSPS NLCA N                 N    72 NIL
6052421600 NODIALTN N Y      INS Y   LATA1     N
                                                                           $

TABLE: CLLI
>quit
CI:
>table trksgrp
TABLE: TRKSGRP
>pos tmoneld 0
         TMONELD 0    DS1SIG
    STD
2W DT WK N 10 10 DT WK 7 0 Y NO NO N N N M 135 UNEQ $
>quit
CI:
>
Customer is requesting b8zs esf dtmf  wink start.

Hope this clears it up. Thanks for your help.
 
IP Logged
 
Reply #4 - Jul 29th, 2010 at 1:07pm

Paul   Offline
Site Administrator
Switch Technician
Southern Maine

Posts: 237
*****
 
My DMS memory is starting to fade (not having access to one anymore) but in TRKSGRP are you sending the customer 7 or 10 digits?

As to the carriers coming up with an RTS and not on their own from a SYSB I've seen that before when the circuit was set to AMI somewhere downstream but you mentioned that the carrier was passing test with an all Zero's pattern.
 
IP Logged
 
Reply #5 - Jul 29th, 2010 at 2:02pm

tsands   Offline
Junior Member
Translations Technician
I Love Telcom!!
iowa

Posts: 6
**
 
I'm sending four digits in table ofrt. Per customer request.

Transmission tech has recheck all muxs. They say everything is set to b8zs. If we loop up all four nius on customer site. We can run all zero's clean on all four carriers.
 
IP Logged
 
Reply #6 - Jul 29th, 2010 at 2:46pm

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
I agree with Paul, it sounds like a setting of AMI somewhere.

All the datafill supplied looks fine.  Another possible item is the EXECs loaded in the DTC and also the firmware.  The EXEC you are concerned about is the ABTRK exec.  IF you have something other than DTCEX, let me know, I'll have to look and see if it works for PX trunks.  The firmware is the blue highlighted item below.  This firmware version is for SN09 in North America.

       DTC   0
              1    DTEI    0    18      1    B     9 6X02NA  ED714BC
                              
(        ABTRK  DTCEX) ( 
   
  AB250 UTR250)$
(0 10 0 0) (0 10 0 1) (0 10 0 2) (0 10 0 3) (0 10 0 4) (0 10 0 5)
(0 10 0 6) (0 10 0 7) (0 10 0 8) (0 10 0 9) (0 10 0 10) (0 10 0 11)
(0 10 0 12) (0 10 0 13) (0 10 0 14) (0 10 0 15) $
                    (CONTINUITY ) (     UTR15 ) (   MSG6X69 ) (   STR16IC )$
     NORTHAM                                                 MX77AA  MX77AA
                                                        0
                            
UPFWNV03

                                                    (    CCS7 ) ( STRDTRE )$
     6X40FB                                            N

 
IP Logged
 
Reply #7 - Jul 29th, 2010 at 2:51pm

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
Would be nice to see an OMSHOW for the carriers.

>omshow ds1carr holding 'HOST DTC 27 2 C'
>omshow ds1carr holding 'HOST DTC 27 4 C'
>omshow ds1carr holding 'HOST DTC 25 5 C'
>omshow ds1carr holding 'HOST DTC 20 16 C'

Be sure the stuff in quotes at the end of the command is CAPS.

If you collect this data on a daily, weekly and monthly basis, it would be best to see a weekly (or daily for different days).  So instead of the HOLDING word in the command you would insert the name from table OMACC used for weekly collections and daily connections.
 
IP Logged
 
Reply #8 - Jul 29th, 2010 at 3:04pm

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
tsands wrote on Jul 29th, 2010 at 2:02pm:
If we loop up all four nius on customer site. We can run all zero's clean on all four carriers.


You would be bipolar violations if something was set wrong when running all zeros.  See if the customer can loop their DS1 card, then run zeros to insure they are not set to AMI.
 
IP Logged
 
Reply #9 - Jul 29th, 2010 at 3:38pm

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
This one is a longshot, but here goes.  The 6X50AB card has dip switches which are used to set line impedance for the gauge and length of the cable from the card to the DSX/DACs.  In order to check, these switches you have to pull the card from the frame (and use procedures for changing out 6X50 cards).

Each 6X50 card has two ports.  Thus if you have a trunk assigned on DTC 27 X 3, DTC 27 X5, DTC 25 X 5 and/or DTC 20 X 17 and they are not experiencing problems, then the dip switch setting is probably OK.  IF there are noassignments on ALL of those T1s you may want to check at least one of the cards.
 
IP Logged
 
Reply #10 - Jul 29th, 2010 at 6:04pm

tsands   Offline
Junior Member
Translations Technician
I Love Telcom!!
iowa

Posts: 6
**
 
Everything is now working. Except incoming to the PBX. PBX vendor says he not seeing it as a DIOD call. Traver shows I'm sending him four digits per his request. He's not seeing anything. Even if I change the number of digits I delete. I have not change any of my datafill. I now have the pbx directly connected to the dtc here on site. Any idea on trkgrp or trksgrp setting or options.
 
IP Logged
 
Reply #11 - Jul 29th, 2010 at 7:09pm

Paul   Offline
Site Administrator
Switch Technician
Southern Maine

Posts: 237
*****
 
In my experience when a vendor is telling me they "Don't see anything" it was usually attributed to the PBX not sending a "Wink" start signal.

This is where I would always grab my trusty hand held analyzer, so if the DMS sends the PBX a call here's the steps:

DMS seizes a trunk member
PBX detects the off hok state and winks the A+B bits
DMS pumps out the 4 digits

At this point that's my suggestion, get someone (or yourself) who is good with an analyzer and plug directly into the T-1 of the DMS.  Watch the supervisory bits for an off-hook state and hit the "Send wink" key and listen and/or capture the digits on the screen.

Sometimes your eyes are the best tool.

Sorry, wish I could be more helpful.
 
IP Logged
 
Reply #12 - Jul 30th, 2010 at 9:07am

mountain   Offline
Full Member
NOC Technician
Denver, CO USA

Posts: 169
***
 
As Paul stated, the customer is probably not winking back.  You can verify this via the logs.  You will get a TRK121 log if a wink is not received:

XXXXXXXX CM            TRK121 JUL30 06:01:11 3100 FLT  OUTPULSING TRBL
        CKT     PAR_CHEV_2W6    1
       
TRBCODE=            NO_START_DIAL
TRBLINFO=
NIL
       
FAILURE=  FIRST_TRIAL_FAILURE

        INCTRK= CKT    COVNCAXF01TLT    1 CLDNO= 5556447214
        DIGSOUT= $ CALLID=      687118


You will get two logs, one which says "first trial failure" and another which states "second trial failure".

« Last Edit: Jul 30th, 2010 at 12:30pm by mountain »  
IP Logged
 
Reply #13 - Jul 30th, 2010 at 5:31pm

tsands   Offline
Junior Member
Translations Technician
I Love Telcom!!
iowa

Posts: 6
**
 
Thanks for the help. It end up being niu setting and bad hardware in the pbx.
 
IP Logged
 
Page Index Toggle Pages: 1
Send Topic Print