We just had to roll back our R9.0.4 ug today on our IP500v2 box. Major problems:
R9.0.4 on the IP500V2 switch software we found 2 major issues:
1) 3rd party TAPI doesn’t work the same as R8.0 and is now unusable.
2) The variable $DDI is not properly passed from the switch to VM PRO and therefore causes all VP scripting to fail with that variable.
The VB Script variable $DDI used to pass the telephone number of the inbound line of what number the outside user called in on. It now passes the telephone number of the HUNTGROUP that the inbound call is routed to instead of the number the user called in on. Major problem unless Avaya has added a new variable we don't know about that captures this critical info about what number the caller originally called.
Regarding TAPI, we used the TAPI version in 3rd party mode that came with R9.0.4 and the debug errors in our code were "Password Error/Authentication Failed". The same version of TAPI R9.0.4 was then used on the 8.0 Switch downgrade and all is working fine with *no* other changes than the downgrade.
So, both of these problems appear to be related to the R9.0.4 binaries on the IP500v2 switch. We rolled back the switch to R8.0 and everything starting working as before. VMPRO is still on 9.0.4, and it appears to work just fine with the 8.0 binaries on the switch. These are the only problems we tried to tackle for several hours with no luck. There may be other bugs, but we just couldn't get far enough to test and discover them.
If anyone has any insight into these issues, it would be much appreciated.
Jeff
R9.0.4 on the IP500V2 switch software we found 2 major issues:
1) 3rd party TAPI doesn’t work the same as R8.0 and is now unusable.
2) The variable $DDI is not properly passed from the switch to VM PRO and therefore causes all VP scripting to fail with that variable.
The VB Script variable $DDI used to pass the telephone number of the inbound line of what number the outside user called in on. It now passes the telephone number of the HUNTGROUP that the inbound call is routed to instead of the number the user called in on. Major problem unless Avaya has added a new variable we don't know about that captures this critical info about what number the caller originally called.
Regarding TAPI, we used the TAPI version in 3rd party mode that came with R9.0.4 and the debug errors in our code were "Password Error/Authentication Failed". The same version of TAPI R9.0.4 was then used on the 8.0 Switch downgrade and all is working fine with *no* other changes than the downgrade.
So, both of these problems appear to be related to the R9.0.4 binaries on the IP500v2 switch. We rolled back the switch to R8.0 and everything starting working as before. VMPRO is still on 9.0.4, and it appears to work just fine with the 8.0 binaries on the switch. These are the only problems we tried to tackle for several hours with no luck. There may be other bugs, but we just couldn't get far enough to test and discover them.
If anyone has any insight into these issues, it would be much appreciated.
Jeff