Avaya Vantage- K155D01A getting error 'meeting ID is invalid'

[sync-by-unito[bot]]

User has to try multiple times to get his login acknowledged by Spaces when he joins his Spaces. User only gets the recording that the meeting ID is invalid.

[sync-by-unito[bot]]

➤ Sudhansu Sekhar Sahoo commented:

Space link: https://spaces.avayacloud.com/u/wesleylynch@avaya.com User email address: wesleylynch@avaya.com When does this happen?: Not on every attempt but often Location: Eastern- Virginia Detailed description of issue: Has to try multiple times to get his login acknowledged by Spaces when user joins his Spaces Error details: User only gets the recording that the meeting ID is invalid. Device with specific HW information: Avaya Vantage- K155D01A, Software version 2.2.0.3, OS Version- Android 8.1.0 Browser version: Chrome version 70.0.3538.110 Speedtest: 22.15 Mbps Android info: Android 8.1.0

[sync-by-unito[bot]]

➤ Umair Aslam commented:

@Ray Gerami ( https://app.asana.com/0/1154145881585295/calendar ) I will be off from Wednesday to Friday. Can you reassign this to someone who has bandwidth?

[sync-by-unito[bot]]

➤ Rohit Moza commented:

@Sudhansu Sekhar Sahoo ( https://app.asana.com/0/1175287792936849/list ) do you have any time range for the incident? Need some time stamps to investigate over.

[sync-by-unito[bot]]

➤ Rohit Moza commented:

@Ray Gerami ( https://app.asana.com/0/1154145881585295/calendar ) Also I see this error coming up for Vantage

22:14:32.633 EDT2020-08-18T02:14:32.633Z - error: [syncInstanceSubscriptionsToAllActiveTopics] [1e67ca318b635b27ddb8bdca9343a37e/7688023512412678635][user:5f3b37b5f97ac11888ec3722] invalid.parameters {"action":"remove","user":{"aType":"anonymous","_id":"5f3b37b5f97ac11888ec3722","displayname":"Avaya Vantage","username":"","picturefile":"","created":"2020-08-18T02:06:45.760Z","secret":"42c4a82aa844a79b","picture_url":"https://accounts.zang.io/norevimages/noimage-anonymous.jpg","profile":{"displayname":"Avaya Vantage","username":"","picture_url":"https://accounts.zang.io/norevimages/noimage-anonymous.jpg"}},"dataOnly":false,"_taskoptions":{"attempts":3,"attempt_times":0}}

Not sure if this is linked. But it looks like subscriptionId is missed in these payloads.

Logan App relevant code snippet:

function syncInstanceSubscriptionsToAllActiveTopics(src, data, cb) { let functionName = '[syncInstanceSubscriptionsToAllActiveTopics] ' + '[' + src.id + ']' + '[user:' + (data && data.user && data.user._id) + ']'; if (!data || !data.user || !data.action || !data.subscriptionId) { logger.error(functionName, 'invalid.parameters', data); return cb && cb(null); }

[sync-by-unito[bot]]

➤ Sudhansu Sekhar Sahoo commented:

@Rohit Moza ( https://app.asana.com/0/1162881603404162/calendar ) There is no time range mentioned for this incident.

[sync-by-unito[bot]]

➤ Rohit Moza commented:

@Sudhansu Sekhar Sahoo ( https://app.asana.com/0/1175287792936849/list ) ok so can you please get some of the information (via emailing the end user) and write it on this asana ticket?

[sync-by-unito[bot]]

➤ Sudhansu Sekhar Sahoo commented:

Waiting for the user's update on the time stamps.

[sync-by-unito[bot]]

➤ Sudhansu Sekhar Sahoo commented:

@Rohit Moza ( https://app.asana.com/0/1162881603404162/calendar ) User made test calls and it failed twice at 11:54 AM EST, 21 Aug 2020. User stated that "the DTMF may not be recognized as he enters Spaces meetings directly from his phone and it fails, if he attempts to enter them manually he can after the second or third attempt".