Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by GHCSCOMM

  1. GHCSCOMM

    Intermintant one way voice

    The patches were up to date after the upgrade. We found that the backplane test errors to be due to NT5D12AC cards. We found these errors not to be service affecting eeven though the Avaya upgrade matrix says that these cards are supported they do cause these errors. We replaced with a NT5D12AH...
  2. GHCSCOMM

    Intermintant one way voice

    What our vendor did was re-downloaded firmware to all the network & controller cards. Problem cleared. We recently up graded to 7.0 & something apparently went wrong according to Avaya. I did an INI and it did not help.
  3. GHCSCOMM

    Intermintant one way voice

    I was able to trace an example. 5370 called 6599 no audio to 6599 but 5370 could hear 6599. .trac 0 6599 ACTIVE TN 052 0 10 13 ORIG TN 020 0 01 08 KEY 0 SCR CUST 0 DN 5370 TYPE 3904 SIGNALLING ENCRYPTION: INSEC TERM TN 052 0 10 13 KEY 0 SCR MARP CUST 0 DN 6599 TYPE...
  4. GHCSCOMM

    Intermintant one way voice

    thread798-1269632 Same issue. CS1000M Rel. 7.0 Intermintant one way voice primarily in group 1 MID-nights % DROL000 DAILY ROUTINE BEGIN % NWS LD30 BEGIN 06:01 26/7/2011 % % NWS401 0 0 2 : -8 -9 % % NWS501 0 0 3 : -5 % % NWS501 4 0 3 : -12 % % NWS401 4 0 5 : -3 -4 % % NWS401 16...
  5. GHCSCOMM

    Incomming DID's to a RAN

    Thanks everyone. I did an IDC table to RAN route.
  6. GHCSCOMM

    Incomming DID's to a RAN

    I will try changing the LDN in switch "A" and see what happens. I cringe at having to set up IDC for all those numbers.
  7. GHCSCOMM

    Incomming DID's to a RAN

    Yes only the NXX is changing. The old DID exchange route is in switch "A" the new DID exchange route is in switch "B" and route the necessary numbers over to "A" via a TIE PRI.
  8. GHCSCOMM

    Incomming DID's to a RAN

    If the carrier send us more digits the switch is only going to see the last 4 with a LDN of 4 digits correct
  9. GHCSCOMM

    Incomming DID's to a RAN

    They want to charge us big time for that. I was hoping I could do something with the switch.
  10. GHCSCOMM

    Incomming DID's to a RAN

    I'm actually recieving 7 digits from Verizon. LDN is set for 2000 ( 4 digits ). Can I just set the LDN to 20000 ( 5 digits ) making it a vacant number.
  11. GHCSCOMM

    Incomming DID's to a RAN

    My issue is these numbers are at the moment working DID/Internal numbers. How do I get the DIDs that have programmed numbers to the intercept treatment? I have at the moment the old DID exchange is in one route while the new exchange is on another route. Both exchanges are working at this time...
  12. GHCSCOMM

    Incomming DID's to a RAN

    Yes, but how do I get the DID calls to the vacant number routing I have INT_DATA set to CTVN (ovf ovf ovf ran).
  13. GHCSCOMM

    Incomming DID's to a RAN

    Ok then now how do I get the DID's to the intercept treatment? Change the LDN from 4 to 5 digits? Will that affect internal or point to point calls?
  14. GHCSCOMM

    Incomming DID's to a RAN

    We have an CS1000M 7.0 with two Verizon DID PRI’s. We are changing telephone exchanges, I need a easy way to take all the incoming numbers ( approx. 6000 ) to this route and send them to a RAN indicating the exchange has changed and to call the new number. If I give them an intercept treatment...
  15. GHCSCOMM

    Lift handset and activate key other than PDN

    I'm aware of the ringing group (IRA OLA LPK) I’m just trying to think of a work around so people internally get the department number not the provider private DN. I tried CLID tables that did not work either. Also when the provider picks up their phone they would get their line key 8 SCR XXXX D...

Part and Inventory Search

Back
Top