Yealink Forums
Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 (/showthread.php?tid=11441)



Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - gr8liquor - 11-14-2015 03:37 PM

Upgraded T46G from 28.73.0.50 to 28.80.0.70. Now we can no longer register to multiple domains using the same user account name(9999) on different accounts in the telephone.

I have this T46G I use for support and to test with. I will often use extension number 9999 in a customers domain to test call flow or record greetings/messages. I have accounts 4, 5 & 6 register to test extensions in different domains on our multi-tenant Freeswitch server.

Example
Account 4 9999@customer1.ourserver.net
Account 5 9999@customer9.ourserver.net
Account 6 9999@customer50.ourserver.net

This worked on 28.73.0.50 and prior.

Now the account that registers first wins. It registers fine and works. The other accounts fail to register.


RE: Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - RUN_Support - 11-25-2015 04:31 AM

I've noticed this too. If all the accounts have the same username they also need the same password in order to work properly.
Yealink should address this, I've been meaning to submit a ticket about this.


RE: Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - imfloridaguy - 12-07-2015 08:23 PM

gr8liquor, did you get this resolved?


RE: Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - RUN_Support - 12-09-2015 02:14 AM

If there are 2 accounts with the same username, the passwords need to be the same too. Otherwise one of them will fail. It's a Yealink bug, but this is the workaround.


RE: Can't have 9999@domain1.com and 9999@domain2.com on 28.80.0.70 - gr8liquor - 12-09-2015 12:17 PM

I went back to the .73 firmware because I hade a display update issue too. I think there's a new provisioning setting to deal with the display update issue, but didn't get a chance to test that.

So No, I did not. I see the other user (JasonNadeau) that made the passwords common on the accounts to resolve this on their telephones. But I don't want any common passwords anywhere in our server. So I will wait to upgrade till this is resolved by Yealink.