Problem with coverage path

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • thrasonic
    Aspiring Member
    • Jun 2012
    • 1

    Problem with coverage path

    Hi all. We changed a very popular number here from a station to a vdn (x4357). It happens to be our helpdesk number. We created a new helpdesk number that is x-ported to be used for providing ringing call appearances on the helpdesk tech’s phones (x6983 – it’s programmed as a 6408d+). We created a vector with time of day routing to work with the vdn. We were worried about people realizing they could circumvent the new vdn by dialing x6983 directly so we were thinking we could use a custom coverage path that points all calls to x6983 to the new vdn 4357. The problem is that calls aren’t going to coverage when they’re routed to vdn 4357. When they’re routed there the tech’s phones ring as they should, and you hear the beep tone after 4 rings indicating it should go to coverage (voice mail) only it never does – it just rings and rings and rings. I setup everything with basic defaults like many other vdn’s and vectors we have and use. Any thoughts? The issue seems to be coming from the coverage path alone so help figuring this out would be great.
    Attached Files
  • qtu
    Aspiring Member
    .
    • Apr 2012
    • 2

    #2
    Hi Thrasonic,

    I'm a Tier 3 engineer from AVAYA,

    .Which products, software version / service packs is/are currently running on the server or platform?

    Comment

    Loading