I upgraded VM Pro (along with the rest of the switch) the the May maintenance release (3.1.56) last night, and all seems OK, except one problem with VM Pro.
VM Pro was previously at 3.1.15, and is now at 3.1.21.
Our incoming calls are routed to a VM Pro module, which tests various conditions based upon CLI, time of day, etc and then decides upon where to route the call (eg. to a group, to another VM Pro module, etc).
Whilst the VM Pro module is working out what to do with the call, the call used to remain unanswered, and presented a ringing tone to the incoming caller.
Since the upgrade to 3.1.21, the call now gets answered imediately and the caller just hears dead-air until the VM module decides what it's going to do (takes about 3 seconds). Once it decides to route it to a group, the incoming caller then gets the ringing sound.
Out curring incoming route is set as follows
Line group:0, Incoming Number: 374757, Destination VM
CSIncoming, Priority: 1, Fallback Extension: PCS, Bearer: AnyVoice
Is anyone else having these problems? Is there a way around it?
VM Pro was previously at 3.1.15, and is now at 3.1.21.
Our incoming calls are routed to a VM Pro module, which tests various conditions based upon CLI, time of day, etc and then decides upon where to route the call (eg. to a group, to another VM Pro module, etc).
Whilst the VM Pro module is working out what to do with the call, the call used to remain unanswered, and presented a ringing tone to the incoming caller.
Since the upgrade to 3.1.21, the call now gets answered imediately and the caller just hears dead-air until the VM module decides what it's going to do (takes about 3 seconds). Once it decides to route it to a group, the incoming caller then gets the ringing sound.
Out curring incoming route is set as follows
Line group:0, Incoming Number: 374757, Destination VM
CSIncoming, Priority: 1, Fallback Extension: PCS, Bearer: AnyVoiceIs anyone else having these problems? Is there a way around it?
