Yealink Forums

Hi,

I've been using Polycom phone for a long time, and I can specify a domain for my SIP user, so example, 1000@pbx.enterprise.com. And that domain is separate from the server name.

But I can't figure out how to do it with Yealink without specifing pbx.enterprise.com as my server name. This causing issues because I want to have 2 separate registration for that user to a failover server.

Also, I do have need to set up 1000@pbx.internal as my user, but when my user is remote, I need to connect to public-ip.enterprise.com, not to pbx.internal.

I've look though W60B manual, and I can't find anything. I tried adding a @ in my user_name field but it didn't work. Does it need to be escaped in some way ?

Thanks

If I understand correctly your question, you'd put the domain in the Server Host field and the server/s in the Outbound Proxy Server field/s.

(03-10-2021 12:20 PM)Yisroel_MongoTEL Wrote: [ -> ]If I understand correctly your question, you'd put the domain in the Server Host field and the server/s in the Outbound Proxy Server field/s.

Urm, I've stop using outbound proxy a long time with polycom (It could caused some issues with some feature). But I'll give it a try. Thanks

(03-11-2021 03:41 AM)Marc Olivier Wrote: [ -> ]Urm, I've stop using outbound proxy a long time with polycom (It could caused some issues with some feature). But I'll give it a try. Thanks

Keep up posted...

Is there is still no way to specify a domain to auth the user with which is different than the Server Host (without using an outbound proxy (which I don't need it as a proxy)) ?

I tried lot of hack, like getting Static DNS-NAPTR setting so I can use the dns in UDP mode to get the server.1 ip, and then use the server.2 with the same DNS name but with DNS-NAPTR with the local static dns ip which would point to a different server... Nothing seem to work.

I'm just trying to connect to the servers via 2 different IP addresses, so the local pbx still need to match the same local domain information. And I need them to register at the same time.

I had this working for years now with Polycom phones, but everytime I try with Yealink, it doesn't work. So before I tell the client to replace their yealink phones, I'm just taking one last chance.

With a little more tweak, I got it to work with the static caching hack using the DNS NAPTR for the second server registration and forcing UDP for the first one.

It not pretty, and we do lose the SRV features on the primary server at a minimum. So it not great, and I won't recommend these phones, I still fixed my immediate issues I think !

You can try with different IP address or use the DNS NAPTR for the second server registration. However, I tried this, but it still doesn't work. How about you.

smash karts