Yealink T48S Phones perfectly working, but 3cx-state not changing to "PROVISIONED"

[PrismaComputer]

Hello,

we have several Yealink T48S Phones. They're all perfectly working. They are pulling their configuration from PBX, they are all registered, line works.

BUT: 3cx-state shown at "Phones" not changing to "PROVISIONED".
3CX Windows Clients are shown as "PROVISIONED", but not the phones.

Why?

 

[Saqqara]

How are the phones provisioned - local , sbc or stun.

What steps do you go thru getting the phones online.

 

[PrismaComputer]

They are provisioned over STUN because It's a cloud PBX. We don't use SBC.
They are provisioned automatically. This means, install the 3CX firmware, login with extension and PIN and that's it.

 

[Saqqara]

Being stun, each phone requires different sip and rtp ports.

Also you need to setup port forwarding on the firewall protecting the phones

more info, check last post

https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296

 

[CentrexJ]

I have a feeling you are using the Yealink T48 option in 3CX provisioning which is for the T48G phone and not the Yealink T48S option in 3CX provisioning. The phone will work fine with either option, however display "PROVISIONED" for the MAC address if you choose the wrong model.

 

[PrismaComputer]

Thanks CentrexJ,

phones are provisioned as T48S and they are T48S. The only way, that something went wrong was that we installed the wrong firmware. That means, maybe we installed a T48 firmware on a T48S ?!?!
How to check this? The filename of the installed firmware is T4XS-66.84.0.35.rom. Sounds absolutely correct.

1. OK, did I correctly understood? We have to expect NO downside if everything is obviously working, but MAC address shows not "PROVISIONED"?
2. Shall we try to provision the phones with SBC (initially? And later change config to SIP/STUN?) ?

I'm a little bit upset about 3CX. It's the second time we encounter problems in absolute standard situation that are (maybe) caused by the fact that the PBX is running in the cloud. Why does 3CX offer this offical possibility if the function is limited?

 

[PrismaComputer]

Thanks Saqqara,

the PBX is in a full routed network in the cloud. Not (!) behind NAT. Are you sure that the post above fits our scenario?

"In the Management Console each Remote STUN Extensions must have a unique Local SIP Port and Unique RTP Port range and the RTP Port range must be 10 ports (for Yealink phones 12 ports) per remote site."

This would mean, every time (!) you use 3CX not local you would have to go through the configuration hell? I can't imagine this

 

[CentrexJ]

It is likely impossible to put G firmware on an S model Yealink phone. There must be something else miss-configured.

Not sure why you are upset with 3CX. How can you be sure you haven't made an error?

 

[PrismaComputer]

@CentrexJ:
"Not sure why you are upset with 3CX. How can you be sure you haven't made an error?"
Ok, my fault. I can't. Let's get back focused on the facts, please. I'd love to explain it later via PM if you're really interested.

CentrexJ, would you please be so kind to give a short answer to my 2 questions above?

Would you also please have a look at Saqqara comment? I'm not sure if this is related to our problem. I'm not sure if it's really a misconfiguration to have all extensions/phones using the same standard ports if the PBX is in a full routed cloud provider network. Also we encountered no drop outs of speech until now, so...

I would really really appreciate that.

 

[CentrexJ]

1. OK, did I correctly understood? We have to expect NO downside if everything is obviously working, but MAC address shows not "PROVISIONED"?
2. Shall we try to provision the phones with SBC (initially? And later change config to SIP/STUN?)

1. If you have mixed up and used the T48 provisioning instead of the T48S template the phone will still work pretty much normally. What won't work is firmware upgrades through 3CX. However this may not be the case since you already confirmed you are using the T48S provisioning option.

2. SBC makes things better, but mostly helpful if you have more than a few phones at the same remote site. STUN works well in small numbers. If you can setup the phones using SBC leave it that way and move along. But I wouldn't set the phones up as SBC just to see if they show the MAC address under phones, it doesn't really prove much.

As to having to configure the firewall at the end where the STUN phones exist, this is an optional configuration step and makes the phones work best but it won't solve the issue you are finding where the phones show "PROVISIONED" and not their MAC under the Phones tab in 3CX. It isn't a required step and generally the phones will work fine without this step.

You must however when using the STUN provisioning, if you have multiple phones at the same remote site you MUST increment the SIP port of phone and the RTP ports.

This is old but explains it.
https://www.3cx.com/docs/manual/configuring-ip-phones/#h.ul2fzupi6t22/

 

[YiannisH_3CX]

Hello @PrismaComputer

Are you using the default 3CX templates or custom ones? Make sure that there are no template updates pending and that the phones are provisioned with the default 3CX template.
Some times old custom templates can cause the phones to appear as "PROVISIONED"

 

[PrismaComputer]

@YiannisH_3CX

Thanks a lot! You gave the solution to this (obviously not existing) problem.
As we wrote in the initial post, we wondered why the state (column MAC address) does NOT change to "PROVISIONED".

And now we hear, it's normal. It has not to change to "PROVISIONED". On the contrary, it would be erroneous if it the column would change to ''PROVISIONED"... Oh my dear...

Sorry, we derived from the behaviour of all other phones, that the correct behaviour would also be "PROVISIONED". But it's not. (You must confess, for some phones it's correct, for some not, it's a little bit confusing) I attached a screenshot of the phones, so you can see, we're not stupid, but confused...

In the meantime we configured all phones with their own local SIP port and RTP range. Does not hurt, but questionable if really necessary...

Once again, thank you all for your help and once again sorry for our confusion.

 

[YiannisH_3CX]

@PrismaComputer

Let me explain how the management console handles different phones. Fully supported phones running the latest supported firmware actually send their MAC address in the registration message in a format we can read and it is displayed in the MAC Address column. For legacy phones or other devices that are provisioned via 3CX but do not include their MAC address we add them as "PROVISIONED" to indicate that they are indeed provisioned. You can also see the word "UNPROVISIONED" in that column for phones that are registered manually but not provisioned.
From your initial description i though that you were seeing that wrong state for fully supported devices. We apologise for the confusion.