When i try to transfer a call via the next gen micollab client, it wouldn't put the call on hold.
This works ok when i do a transfer by using the handset.
If it's only the MoH itself and transfer is fine, it sounds like a network/SIP related problem with the audio stream when you send a SIP request for the music on hold. Do you use the recommended default SIP device capabilities number for your softphones? Should be 71.
Is the MiCollab Client using Teleworker? When the problem occurs is the client located inside your corporate voice VLAN or outside over the internet? If it's inside, do you have the same problem outside or the other way around? Does the problem occur with internal calls and/or external calls?
Doing a SIP capture of the problem on MBG if you're using Teleworker could show some light on this.
That's why I asked OP if the transfer was working fine. Otherwise the missing 2nd multicall would be the problem.
Since the transfer works, he has a 2nd multicall key.
I will check the below -
Micollab Client Service >> PBX Nodes >> Edit PBX >> SIP Conference FAC (Feature Access code)
Make sure this value is the same as the Conference Call FAC in MiVB
The Transfer button in MiCollab Client places the call on hold once the destination to be called is selected. If you just press transfer, you are still talking to the caller while you look up the destination.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.