09-29-2017 01:54 AM - edited 03-18-2019 01:30 PM
Hello,
After we upgraded the customers TMS to 15.5.0 they have gotten the follwing errors on some of there allready boked meetings but not all.
On the meetings with theese errors we can see that the connection alternative have changed from [H323] to [H323-SIP].
Note that the meetings still works as long as you don't edit them.
I tried to search for similar errors but not been able to find any.
Best Regards
Urban Falén
Solved! Go to Solution.
01-29-2018 10:17 AM
09-29-2017 09:47 PM
01-29-2018 05:29 AM
What software version was TMS prior to upgrading to 15.5? unsure, but it was 15.0 or above.
Are these point-to-point or multipoint conferences, and what endpoints/conference bridge is involved? multipoint conferences
What protocols is everything configured to use, ie: H323 or SIP? H323
Do the endpoints and conference bridge have the correct Allow Booking option checked in their settings within TMS, ie: inbound/outbound H323/SIP? unsure seeming we have no direct contact with the customers envoirment.
What happens if you edit the conference and refresh/fix the connection issues, does the error go away? As i understand it from the customer it did.
Have you ran Conference Diagnostics under Admin Tools > Diagnostics, and attempted to have TMS fix the connection issues? No, we never tried that seeming the booking still seemed to work.
Note that when making new bookings this error never occured. Also added som pictures if this helps
01-29-2018 10:17 AM
01-30-2018 01:18 AM
Hello,
Thank you for your help trying to find the reason for this error. This error will solve itself seeming new bookings don't get this error. However, should it return the Conference Diagnostics might be helpful to solve this or as you also mention changing the booking method.
Best Regards
Urban Falén
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide