Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Micollab Mobile and iPhones "Unable to answer incoming calls" 1
- Thread starter Keowolf
- Start date
Find out your Mitel Connect admin by looking under self service, they can then add the options that are missing.
Looks like Mitel will be moving most things out of MOL onto Connect, Knowledge base Bulletins etc have already moved, TechCentral Tracker & Downloads will be moving soon I believe.
Looks like Mitel will be moving most things out of MOL onto Connect, Knowledge base Bulletins etc have already moved, TechCentral Tracker & Downloads will be moving soon I believe.
-
1
- Thread starter
- #8
lowradiation
Technical User
I came across the same issue with a customer today.
Found that if the user has their status set to an option where the softphone is unchecked, then you will not get the answer button on the smartphone app.
eg. If their status is set to "In the Office" and their desk phone is checked but the soft phone is unchecked, the app will still pop up notifying of an incoming call, but there won't be an answer key... checked off softphone and the answer key appears.
Found that if the user has their status set to an option where the softphone is unchecked, then you will not get the answer button on the smartphone app.
eg. If their status is set to "In the Office" and their desk phone is checked but the soft phone is unchecked, the app will still pop up notifying of an incoming call, but there won't be an answer key... checked off softphone and the answer key appears.
Hi!
I ran into the same problems! But it was not any problem of the Release 8.0 or 7.3
The main innovation of 8.0 are only the push notifications via CallKit to Apple devices.
My first problem was: If any User was defined as Multi-Device User, the MD Group was NOT created in MiVb automatically.
So i had to add a Multidevice Group first.
Well, the Decives was now applicable in "my ring group" but i was still unable to pick up the call on my mobile (only the red button) (The strange thig: In MiCollab Web Client - everything worked fine)
After some trial&error hours I was looking on AMC Server, and I was wondering about the "AMC Known IP Adress"
So my Firewall-Guy did not set the IP Adress to 1:1 NAT in DMZ (MiCollab with Webproxy in DMZ)
After setting all the traffic in & out through that specific DMZ Port everything worked fine!!! But who cares, it took only a few hours to find any hint
PS: Micollab Web is working over WebRTC, so the Communication is quite different to MiCollab Mobile
PLUG n PRAY
I ran into the same problems! But it was not any problem of the Release 8.0 or 7.3
The main innovation of 8.0 are only the push notifications via CallKit to Apple devices.
My first problem was: If any User was defined as Multi-Device User, the MD Group was NOT created in MiVb automatically.
So i had to add a Multidevice Group first.
Well, the Decives was now applicable in "my ring group" but i was still unable to pick up the call on my mobile (only the red button) (The strange thig: In MiCollab Web Client - everything worked fine)
After some trial&error hours I was looking on AMC Server, and I was wondering about the "AMC Known IP Adress"
So my Firewall-Guy did not set the IP Adress to 1:1 NAT in DMZ (MiCollab with Webproxy in DMZ)
After setting all the traffic in & out through that specific DMZ Port everything worked fine!!! But who cares, it took only a few hours to find any hint
PS: Micollab Web is working over WebRTC, so the Communication is quite different to MiCollab Mobile
PLUG n PRAY
- Status
Similar threads
- Question
- Question