Micollab Deployment

[boycey9]

Has anyone managed to get the New Client working with the New deployment tool, Instructions seem sketchy and not sure I have all settings correct, The errors I get on the client are cant contact deployment server on first attempt then No Data on server on subsequent attempts

 

[TLDuk]

Trying to set this up myself today and getting nowhere

If its not broke tweak it..

 

[TLDuk]

So its turns out everything I setup was correct the only missing piece was the MBG / MiCollab require valid 3rd party certs for the mobile deployment to work ! the mobile client will throw different errors but in my case SSL/TLS1.2 negotiation is failing..

Very poorly documented feature

If its not broke tweak it..

 

[boycey9]

I did eventually find this documented in the MSL engineering guidelines, talk about spread about

 

[Hawaii5O]

were you able to deploy the Softphone in Teleworker mode? i have everythign working but the releworker. I get no audio. If I use the older 6.0 client teleworker works fine if I modify the advance settings to be UDP for the SIP ptotocol.

 

[TLDuk]

Yes I did get it working, but your problem is more probably firewall issue as the soft phone uses TCP SIP-TLS on port 5061 by default, the mobile sip settings can be changed in the deployment tool for the version 7 client anyway

If its not broke tweak it..

 

[boycey9]

Check for security software on the phone we had a similar issue on one device and removing it fixed the problem.

 

[Hawaii5O]

My deployment profile is set to use UDP port 5060. In the 6.1.304 Micollab for Mobile I have the option of manually changing the Port to UDP 5060 and this seems to work fine. For the 7.0 client are you sugesting that I request the IT admin to open port 5061 TCP SIP-TLS? How would I verify that port is open. I used the TNA to verify the required ports and I don't remember seeing 5061 as one of the tests. Does modifying my deplyment profile automatically change the settings on my mobile device?

 

[TLDuk]

no annoyingly 5061 is missing from the TNA tool the only reason we found out about this was going over a wireshark trace on a working MBG

If its not broke tweak it..