SIP Emergency Routing

[Gui75]

Hi all,

I am investigating SIP Server Emergency Routing functionalities.
What I want is to route to an ACD queue if router is down or does not respond.
And I want this ACD Queue to depend on the RP targeted.

So that I can not use default-dn option at SIP Server level.

I tried to use ACD Queue association textbox, configuring RP in it but it does not work.

From what I read in the doc :

[i]The call flow for this functionality is as follows:
• Agents log into the ACD Queue.
• An inbound call arrives at the ACD Queue and at the associated Routing
Point. The call is not auto-distributed to an agent in that ACD Queue.
• A Universal Routing Server (URS) strategy on the Routing Point selects an
available agent in the ACD Queue.
• The call is routed to an agent's DN, which responds with a SIP Ringing
message. As a result, an EventDiverted message is distributed against the
ACD Queue and EventRouteUsed and EventDiverted messages are
distributed against the Routing Point.
• The agent answers the call.[/i]

This paragraph does not make any sense : how can a call arrive at the same time in ACD Queue and RP.
If sbdy could explain it to me...

[Fra]

It probably means that the agent is logged in the ACD Queue and the Routing point is just where the call is distributed from.

[Gui75]

Hi Francesco,

I do not think this is the meaning, if so what is the purpose of associating ACD Queue to RP?

[cavagnaro]

Hi,
On what document did you read this? Would like to see the general context.

[kowari]

That isnt talking about configurng that ACD queue in genesys as a routing queue is it?

[Gui75]

Hi, Please refer to SIP Server deployment guide, Support for associating an ACD Queue with a Routing Point to understand the general context

[victor]

There are a lot of states (and countries) that require emergency routing to be supported, and by default it seems like VoIP GW is responsible for actually delivering the call to the destination.

By configuring an emergency route point on SIP T-Server and then setting VoIP GW  accordingly, you can override that behavior.

I am a little bit uneasy about this option, because until now, you had a clear demarcation: URS routing first, if fails then PBX routing. Now, you have URS routing, if fails then SIP T/S default-dn, if that fails then VoIP GW. So, in a way, I am not clear as to advantages of having default-dn in between, if you still need something should SIP T/S decide to go to Tijuana and see a donkey show.