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!

Register Log in
  • Congratulations John Tel 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. SouthernKnight

    Avaya Workplace

    As stated, I would think having them enable send-calls and having a coverage path enabled would be one of the easiest things to do. Or you could have them turn on call-forwarding as well to another user.
  2. SouthernKnight

    Inbound EC500 not converting to Internal Extension

    So the issue is still not resolved BUT we do know what is causing it. The MST trace showed us that the screening attribute was not/is not being sent with the call data from Lumen. At this particular site we are testing with we have one of their older Adtran devices performing the SIP to PRI...
  3. SouthernKnight

    Inbound EC500 not converting to Internal Extension

    After finally getting an Avaya SME to do a MST trace we may have the solution. I'll write it up and post it after Lumen makes some changes and I verify it.
  4. SouthernKnight

    Inbound EC500 not converting to Internal Extension

    001, I have moved that 1 everywhere lol. Put in dial prefix, put it in the phone number, left it off. Sadly same results. Incoming call handling is the same as it was prior to moving to Lumen. I've also tried a few things there as well, such as in case it was getting 11 digits to strip 1...
  5. SouthernKnight

    Inbound EC500 not converting to Internal Extension

    We recently started moving some of our voice circuits from Verizon to Lumen. All of that itself is going fine. However, since we have moved we have noticed an oddity... In the past, on the Verizon circuits, if a user with EC500 calls their own DID it would convert the inbound EC500 number to...

Part and Inventory Search

Back
Top