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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. DEEPest

    1408 distorted on 7.0.31 analog lines

    I too have the same issue of static and echo bursts but on 1616 and 1608 sets at one of the sites. I too have gone through the painful process of changing 1. Combo cards ( the main board should be at firmware PCS 7 and the d/b should be at pcs 10) : REF: PCN Number: 1786B. 2. Changed the main...
  2. DEEPest

    Integrating Cisco Unity with 81C 25.40

    Thanks pndscm for your inputs!!! Really valuable
  3. DEEPest

    Integrating Cisco Unity with 81C 25.40

    Really appreciate your answer on this. But there would be a possibility of VM users encountering busy signals with this (broadcast hunt) setup. At your site you installed is there any such complaints? I see a section on "CPID" in the integration guide. Does this need to be programmed for this...
  4. DEEPest

    Meridian 1 integration with Cisco Unity

    John, I tried building a ACD DN which forwards to the first DN of the PIMG |(supposedly the hunt DN for the VM). In this scenario : even the first caller fails (gets generic greeting instead of requesting to punch in the mailbox password). Basically, with ACD too M1 brings in the forwarding...
  5. DEEPest

    Integrating Cisco Unity with 81C 25.40

    Integrating Cisco Unity with 81C 25.40: 2616 sets emulated to the PIMG box. Followed the procedure as per Cisco guidelines: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/pimg/guide/cucintpimg090.html#wp1060852 2616 ports are hunting/fwd'ed to the next port and so on...
  6. DEEPest

    Meridian 1 integration with Cisco Unity

    Integrating Cisco Unity with 81C 25.40: 2616 sets emulated to the PIMG box. Followed the procedure as per Cisco guidelines: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/pimg/guide/cucintpimg090.html#wp1060852 2616 ports are hunting/fwd'ed to the next port and so on...
  7. DEEPest

    Secc 4.2

    Hi, Cannot get agent Real time Display to work. It opens and closes right away. All the other RTD works i.e. skillset etc.. Have anybody encountered this issue before. The Event Viewer - Application - gives event 1000 : nicgrdsp.exe Updated all the patches but still the same.
  8. DEEPest

    Historical Reporting on a Co-res CC6

    Thanks DJ!! Well, this was before the DST in March. It's almost more than few weeks now. Thanks again. Maybe I'll try the hotfixes and see whether it makes any difference. Seems like a d/b issue in CCMA for historical reports (time) only. Strange !!
  9. DEEPest

    Historical Reporting on a Co-res CC6

    Installed a CC6 co-res. During install made a small mistake of not checking the Time zone correctly. Corrected the issue by changing the time zone accordingly. Unfortunately now the CCMS has the right time.RTD has the right time. Only when pulling the Historical reports the result is an hr ahead...
  10. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    I finally got it to work. CLS = MBXD should be allowed. Found it through the Nortel solutions d/b.
  11. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    9201, I'll have to get the IVR guys to do that. Not sure whether they are around. John, How do you toggle supervision? Mine is set for THFD.
  12. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    Absolutely, this is one of the first things I tried as the call is trasnferring from a ISDN to a TIE -DTI trunk.Tried that too John. DITI and EXTT and TRNX to "YES" but still does not work. Call works when I do ISDN to ISDN transfer for LD.
  13. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    Sorry, NCOS on the IVR set is 4 and under RLI the FRL is set to 4. NCTL has FRL/NCOS set to 4. So there is not problem. Also, MFRL is set to 0 for the LD RLI. Not sure where you can list the station FRL? But as MfRL is 0 it should not matter.
  14. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    What is the NCOS/FRL of the IVR Agent? NCOS on the IVR agent is 4 TGAR is 0 What NCOS/FRL does it take to make a LD call?" FRL (RLB)for the route is 2. NCOS on the members of the LD Tie route is 1.
  15. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    The call goes over PRI but not over the DTI. I guided one LD prefix to a different trunk route(ISA) and it works.So it is some mismatch to do with DTI Tie trunk trunk group. It drops the call.
  16. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    Hawks, 9201 suggested that I dial the IVR DN directly and when I did that I hear a click and the call drops. I see in the ENTC (enhanced) trace that the call tried to connect to Long distance Tie route but for some reason drops.
  17. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    Yes it goes through NARS/BARS. Option 3 for example is local 972 which is routed to RLI 1 with route XX which is part of the master ISA route. This works fine. But the LD calls go over RLI 2 which has Route YY programmed as TIE. 1-800-xxx is dialed which is converted to YYYY by the CO...
  18. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    IT could be emulated by conveting the IDC to a test Analog set andtrying to transfer from there. This would narrow down the problem further to the third party IVR box. But I think it is a PBX issue.
  19. DEEPest

    Incoming calls cannot be transferred externally when it's LD

    Only difference is that for local it takes a COT service circuit which is part of the master ISA route. Whereas for LD it takes a Tie route which is not part of the ISA route.

Part and Inventory Search

Back
Top