Micollab softphone - register fail

[luxmitel]

Hi,

I've implemented a micollab on LAN mode on cluster with a vMBG on DMZ Mode.
The users have intregration with the Active directory.
All the 3 tests on the micollab deployment diagnostic are ok.
The micollab client on the pc on the client Lan and from the internet is ok.
The micollab softphone with the corporate WIFI is working.
The problem is, when i want to connect the softphone using the external WIFI or the 4G the application micollab client mobile is working but the softphone give register fail.
on the tug.log of the Micollab I see the register users, my softphone number there.
One thing that i found is on booths VMBGs, because they are on cluster (vmbg micollab and vmbg DMZ),
on the sip devices field, an example SET-SIDE USERNAME mig-22*4 BAD PASSWORD.
Every time when a configure a new user by Active directory, on this field i have always SET-SIDE USERNAME mig-xx*x BAD PASSWORD. I think the problem could be from here.
Have you some ideas why this happened and how to solve it?

Thanks you

 

[danramirez]

Have you tried manually
setting a new password for that user on the MBG?

http://www.hatkanatelecom.com

 

[luxmitel]

I've changed manually the password on set side password field. Now i do not have anymore the error Badpassword.
I tested the softphone and i i've the same issue. register failed. i thought that could be because I have changed the password so i deploy again the client on micollab client deployment to send me a mail with QR-code. I tested but i have again the register fail.

 

[Billz66]

change all the passwords

change set side , ICP side on MBG
change SIP user account password on MiVB

then go to the client deployment blade , locate the account and resync , then redeploy it

If I never did anything I'd never done before , I'd never do anything.....

 

[luxmitel]

I've done and the softphone still on register failed.
I saw on the logs that he stay pending on the MiVB tug Log du Micollab:
Trunks:
2018-01-18 09:27:37.288
2018-01-18 09:27:37.288 Registered Users:
2018-01-18 09:27:37.288 39 damovo-22*4 -> 22*4@10.100.0.11:5060 #reg-pending:0 #reg:0 Uptime:0d00:00:18 mapCID:0
2018-01-18 09:27:37.288 Mac:39:0D:95:3A:37:38 Addr:10.0.4.225:53989 NAT:10.0.4.225 TW:0 Type:GENERIC (-reg +AUTH -trusted) (17s) reg-idle:86400 reg_pending:0 UDP #CallId:0
2018-01-18 09:27:37.288

the 10.100.0.11 is the MiVB

 

[luxmitel]

Sorry. Thoses logs are not the good one. Those are when i connect the mobile on Wifi corporate and works. When i use the 4G on the tug logs of the micollab on " Registered Users" is not showing nothing.
Could be because i'm using a cluster between the vmbg of the micollab on mode Lan and the vmbg on mode DMZ?

 

[Wishforall]

Hi,
Make sure that under MiVoice Border Gateway > System Configuration > Settings. Go down to SIP Options and make sure TCP and TCP/TLS is ticket.

Kind regards,
Wishforall.

 

[Waldosworld]

What version of MiCollab?
In version 8 they have made changes.
In the MBG you will see the username changed to username-ext#

 

[luxmitel]

Hi Waldosworld
m using the micollab version8
I needed to add on the deployment client the vbmg on DMZ and not use the local vmbg.
Now is working

Thanks to all of you.

I've a great day.

 

[jpruder]

Did you check that the sip settings allow udp,tcp and ssl? I also add that in the network of the controller

 

[luxmitel]

Hi all,
it was the port 443 between Lan and vMBG and the cluster between vmbg from micollab and VmBG on DMZ

Thank you all.
Lux

 

[bobbai]

Hello Lux,

Can you explain in a little more detail what you did exactly as we're having what sounds like the exact same issue and we're really struggling to get this working.

Thanks,
Bob

 

[TCSI17]

Hi,
If you are having issues with MiCollab Mobile, make sure of the following:
0) Cluster your MBGs
1) You need to create a connection to your external MBG. Do this in the MiCollab Client Deployment-->Configuration-->Connection to MBGs (not using the default one in MiCollab). Create a new connection to MBG and use your DNS name that resolves to MBG.
2) You need to create a NEW MiCollab Deployment Profile and in that profile, select the newly create connection to MBG as per #1 above.

That should solve issues.
I found also if you are having issues with SIP Softphone on MiCollab Mobile not registering, it could be the certificates. You can try and uncheck the 'verify TLS' within the deployment profile and see if that solves the issue.
You need to ensure that DNS is properly configured in a SPLIT DNS fashion. Did I also mention, you need to make sure your DNS is configured properly?