Search results for query: *

if you are going to do your routing for 9plus numbers in cisco then translate you 9 in cisco to the pri route access code on nortel example you want 918005554141 send acod for pri route ie; 8000 18005554141

you can set up new route with trunk example config route as cot trunk tn should be ground start set up trunk tn as auto terminate to dn of 3902 you can at least recieve calls from trunk and you can make outbound as normal.

on the subject of telnet, you should be able to attach tty port to a pc connected to lan and telnet from any pc then use normal login same as tty

try setting mwc=yes on acd dn

YOU CAN USE CALL TRACE (LD 80) HAVE SOMEONE PLACE AN ONNET CALL TO AN EXT HAVING THE PROBLEM AND THEN TRACE THE CALL TO SEE WHAT ROUTE IS USED, TRAC TN(ie 4 0 02 0)NOTICE THE "DIAL DN" FIELD THIS SHOULD TELL YOU IF THE CALL IS COMMING ACROSS TIE LINES IF IT IS (ORIGINATING TN) THE...

EJPTELECOM, GLAD YOU GOT YOURS TO WORK , I POSTED THE PARAMETERS FOR THE SAME APPLICATION AS YOURS, EARLIER IN THIS THREAD , I'VE DONE TWO AND DID NOT NEED QSIG.

is 14 a new did route? it has no idc entry? if this is for a new block of dids would't you need an idc table for it to translate? there is no modifications of digits in bound on tie lines are the onnet calls comming across tie lines?

AND IF AVAILABE TRY A LOOPSTART POTS LINE ON A PORT PROGRAMMED AS LOOP TO SEE IF YOU HAVE A HUM ARE THE TRKS ON A SLIC FROM CO THEY MAY NOT BE SET RIGHT

2 THINGS I WOULD DO 1)VERIFY GROUND START OPERATION AT DEMAC WITH TEST SET. MAKE SURE ITS NOT LOOPSTART AND POLARITY IS CORRECT. 2)VERIFY JUMPERS ON CARD ARE SET FOR CO REFER TO PLANNING AND ENGINEERING,TRUNK CARDS NTP FOR CORRECT VINTAGE

IF YOU CAN RECIEVE A CALL ON THE ANOLOG CARD YOU SWAPPED AND CAN XFER TO AN EXTERNAL NUMBER , BUT THE THE IVR AND LINE SIDE T-1 ISN'T WORKING IT SOUNDS LIKE THE IVR ISN'T PERFORMING XFER CORRECTLY, IT HAS TO FLASH HOOK AND DIAL THE DN SAME AS YOU DOING IT MANUALLY. SOMEPART OF THAT TRANSFER...

SONOMARZ LD 22 REQ ISS LD 49 REQ PRT TYPE IDC DCNO (RETURN) (JUST A FEW AS AN EXAMPLE) FROM WHAT YOU SAID YOUR RECIEVING 4 DIGITS FROM DID ROUTE AND THIS IS TRANSLATING TO 3 DIGITS LD 21 REQ PRT TYPE RDB CUST 0 ROUT (YOUR DID AND TIE LINE ROUTES) IN DID ROUTE NDIG=?,IDC-?,DCNO=? IN TIE LINE...

perry is right it could be a supervision problem, And on your FSUM print there is a problem in that you are behind in the firmware on the 3903 sets Your current software 25.30 expects that your 3903's run the firmware thats on your disk-looks like you may have upgraded system to 25.30 and...

TRY USING A SEPERATE ROUTE LIST RLI FOR THIS IN 86 AND A NEW DMI IE: DMI=10 DEL INST CTYP=SPN

CISCO MUST DELETE THE 8 ON CDP CALLS TO YOU SET NCOS ON TIE LINES HIGH ENOUGH TO ALLOW DIALING LONG DISTANCE

ld 32 type FSUM POST THIS REPORT HERE WITH YOUR SOFTWARE RELEASE

need more info , can't tell what your doing

you are not doing any thing wrong. and internally you say you can't dial 124.1234 can you dial 1234? are you using tie routes, if so check to make sure that the rdb is not somehow inserting 123 and make sure whatever switch you the tie lines are connected to are not inserting 123. now that...

print your idc table and ld 87 prt hloc and lsc's sounds like hloc or an lsc is your old exchange

ni-2 is national, is the central off set up nat'l or custom? custom is AT&T'S way usually if it is nat'l post a capture of the dch prt . and rdb prt

need some help please any instructors or engineering types?