It’s about Avaya Communicator for Android on a mobile phone with VoIP Call. CES activated and Ring-Also goes to mobile phone.
When I lose data connection to SBCE on my mobile phone, SBCE sends a “service unavailable” back to CM. CM immediately creates a new call to my mobile phone number, but that call fails:
The connection between the Android and the SBC was dropped and then we started the test calls:
Call1: Calling party 0xxxxx1255. Called party ext 9313 UID 8C96 tries to reach the Android but SBC replies Service Unavailable, then CM starts the EC500 call, Android rings and shows the number 9313, after going off-hook at the Android end you hear ringback at the Android and the caller at 0xxxxx1255 hears ringback as well.
Call2: Calling party 0xxxxx1255. Called party ext 9313 UID 8C96 CM uses EC500 to reach the Android. It rings, shows the calling party number 0xxxxx1255 and not 9313 as before and when you pick up the call you get normal talkpath.
When waiting 15 seconds after the connection between the Android and the SBC was dropped the first call works fine as well.
