Avaya VDN is not picking up call

[aizham]

Macca,

I have set 'route-thru-queue' to true but it still doesn't work.

[cavagnaro]

I find this strange:

[code]
@22:09:46.3790 [<<] 08 00 00 2A 08 02 BA 4F 62 96 1C 22 91 A1 1F 02 01 02 02 01 95 40 17 08 02 81 E5 0C 06 80 23 23 23 23 23 10 02 16 CB 96 44 01 81 47 01 84
  TP_AsaiData
  FACILITY  CRV:ba4f
  Facility: INVOKE
  InvokeId: 2
  Operation: EventReport
  Cause: 101
  ConnectedNum[1]: (unknown),'#####'
  CallID[1]: 5835
  PartyId[1]: 1
  Event[1]: Disconnect
@22:09:46.3790 [asai] (processEvReportDisconnect)
[/code]

From where does that #### comes from?

[aizham]

I might sound stupid but i really don't have any idea about '####'. Is it something to do with the VDN setting in the switch? Anybody face this problem before?

[cavagnaro]

Not stupid at all...nobody can born learning everything. I like the fact you want to learn...

Ok now, maybe Fra already gave the solution:

Lets try to understand this:

You have VDN A monitored by Genesys
You have VDN B not monitored by Genesys

On VDN A you have a loaded strategy so Genesys can do its cool stuff here and after that you want to route the call to VDN B so your Avaya takes control but now with any Genesys involved, right?

So, on your strategy loaded on VDN A just use TRoute("XXX","","") where XXX is the number of the VDN B you want to transfer to...

[aizham]

You are right. I have done it as what you mention but still my call get disconnect in VDN B. I have done some internal testing (extension --> VDN A --> VDN B) and it works. Whenever i call from outside number (DID number --> VDN A --> VDN B) it doesn't work.

[cavagnaro]

Even with TRoute? If so, paste your TServer logs but also indicate calling number, called number, VDN numbers as well.

[aizham]

Finally i manage to solve the problem. I don't know whether my solution is correct or not. In VDN A there is a VECTOR which i add in an announcement playback to delay the call before the adjunct link 1. It seems to work after adding the announcement. Is there any time synchronization between Genesys and the Avaya switch?

[Fra]

Yeah, vectoring rule #1, always add a ringback/announcement at least 1 sec long before an adjunct, don't ask me why! It shouldt be added to some Avaya cookbook or to the next Tony's rough guide

[aizham]

Thanks guys. You all have been very helpfull.

[cavagnaro]

Good to know we helped 

[astrakid]

is this still valid (announcement etc. for at least 1s)? because in our environment we start all genesys-relevant vectors with "wait-time 0 secs hearing i-silent"...
and still everything is worging (avaya definity).

regards,
andre

[Fra]

For me it is, even if I have noticed that it may work also without. But I do know that to be 101% sure you have no issues at all, the 1 second rule is valid, before getting crazy to know what happens to you calls.

Fra