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 Mike Lewis 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: *

  • Users: edoo
  • Order by date
  1. edoo

    Systemwide OLI setting

    Great... now how would I find out which DNs are assigned to the primary 4 channels? As for the B Channels, how does the nam use these vs the A (primary)channels? BTW, I can't find the documentation for our NAM. Does any one know where it can be downloaded? Thanks!
  2. edoo

    Systemwide OLI setting

    It's an 8 port NAM.
  3. edoo

    Systemwide OLI setting

    Thanks for the post... The DN for our voice mail is 301. (Feature 985) I set the OLI for 301 and the nam is not able to complete an outgoing call on our pri. Is there more than one DN for the nam? Thanks!
  4. edoo

    Systemwide OLI setting

    Our provider wants our ICS to send out our BTN before it makes any outgoing calls. It's a way to validate and bill our calls to our account. I have programed the OLI on each set to our BTN. We can complete calls without any problems. Is there a way to make this a system wide setting? Can...
  5. edoo

    Troubleshooting "User Busy" on PRI

    Serviceboy, I made line 157 private to prime. Prime set is 221. Still not any better. I am making the call from the same pri. Looking at the link status I can see my first call is going out the last B channel (#9) and coming in on the first B channel (#1). Once the first call is put on...
  6. edoo

    Troubleshooting "User Busy" on PRI

    Yes, ext 221 (which has 5 appearances for line 157) has 5 intercom keys.
  7. edoo

    Troubleshooting "User Busy" on PRI

    serviceboy, What type of issues have you seen with 6.0? (related to pri) Something else that is interesting.... I am actually switching my pri provider. I did not have this same issue with my last provider. Do you think it could be something on the telco side that is making the slow busy...
  8. edoo

    Troubleshooting "User Busy" on PRI

    bwtc, I don't believe it appears or rings on any other ext. I checked a couple of likely extensions but not all. Line 157 is answered and routed by the receptionist. Therefore it should not show up on any other extension. When the receptionist is not around, ext 221 is forwarded (feature 4)...
  9. edoo

    Troubleshooting "User Busy" on PRI

    Thank you for your suggestions. I made the changes to the line, number 157. It is now set to rings only with 5 appearances. (This setting slipped my mind. Thanks!) I was very hopeful when making my first test call. However, I still got the slow busy with release reason 17. Any other ideas?
  10. edoo

    Troubleshooting "User Busy" on PRI

    I am setting up a MICS rev6.0 on a standard PRI. I am having issues with one of the DIDs sometimes coming up user busy. When I call this DIDs, the correct set rings, it is answered and a long conversation takes place. If another call is immediately made to the same DID (while the long...
  11. edoo

    Resolving Conflicting Destination Codes

    Nope. This was part of a bigger puzzle in routing DIDs to other offices. I've gone about solving the destination codes by not using any codes that are valid DNs. I'm using Destination Codes 477 and higher. Seems to work ok. Not ideal but it works. Dcnsan, What Destination Code are you...
  12. edoo

    Routing DIDs between two MICS

    JerryReeve, It looks like we are using a Coordinated Dialing Plan System 1 has unique lead digit of 2 System 2 has unique lead digit of 5 System 1 has Destination Code of 5 absorbs 0 and uses Route001 over PRI-B The routing of internal call works great. Dialing any ext5xx will reach the...
  13. edoo

    Routing DIDs between two MICS

    Yes a BCM would be very nice to have. Unfortunately it's out of the budget.
  14. edoo

    Routing DIDs between two MICS

    The Goal: When a user moves locations, they wish to keep their current DID. I wish to re-route their existing DID to an extension on another site. Current Setup: • Telco sending 3 Digits • DN Length 3 • DID Block 616-2400 to 2419 • Destination Codes 9(pri), 5(other site) • Routes...
  15. edoo

    Resolving Conflicting Destination Codes

    It turns out that you are all right. 419 is a valid DN. I did a little reading and found out that on a 6 port expansion cartridge, B1 DNs go from 221 to 348 and B2 DNs go from 349 to 476. This is why the first Destination code I'm able to use is 477. I guess it's impossible to create...
  16. edoo

    Resolving Conflicting Destination Codes

    Disabling port 419 does not seem to work. The Destination code is not accepted. So.. Next I thought I would try changing the DN. I checked the status of the dn 461 and nothing came up. I figure it would be ok to use... I hope. After the change, the status of 419 came up with nothing. DN461...
  17. edoo

    Resolving Conflicting Destination Codes

    Sorry... my last post was incorrect. (I was looking at DN420) Here's the correct info Port/DN staus for DN 419 comes up as: Port: 0507 B2: 419 State: unequipped Device: None Pressing the >B1 gets: B1: 291 State: idle Device: ATA Interesting note... the highest DN that the system accepts in...
  18. edoo

    Resolving Conflicting Destination Codes

    Port/DN staus for DN 419 comes up as: Port: 0507 State: unequipped Device: None B1: 420 B2: 292 Hmmm... What if I were to disable it?
  19. edoo

    Resolving Conflicting Destination Codes

    I'm stumped creating a destination code of 419. The system will not take the last digit 9. The system accepts the 4 and 1 but not the 9. I've looked around the system for conflicts and have resolved all that I have found. Here's where I have looked: • Target Line Rec'd # for lines 157-284...
  20. edoo

    Can Hunt Groups be answered by an Auto Attendant?

    Mcbob, I can't believe it works! It's a round-about work-around but I understand how it works. Very creative. Thanks. There seems to be one side effect. An un-answered call gets routed to the AA perfectly. After the call is terminated, apox 30-45 seconds pass then x221 gets an incoming...

Part and Inventory Search

Back
Top