this may happen only of you do stateless processing. If you use TM (t_relay) CANCEL will send automatically to same destination as INVITE. So when INVITE comes, even if user B is register, t_relay will force the CANCEL to take same path as INVITE, which means to VM.
bogdan
Ingo Wolfsberger wrote:
Hello,
Following situation: t+0: User A is registerd User B is not registered
t+1: User A calls user B Call is transfered to the vm box. vm does not go off-hook.
t+2: User B registers
t+3: User A hooks on, a CANCEL is send.
Currently I handle a CANCEL like an INVITE, which means the CANCEL is sent to user B and not to the vm.
How to handle this case?
bye, Ingo