SOLVED Migration to Incredible PBX 2020 is worth the work

[redstonemason]

I am seen on this forum as endorsing PBX 2020. And I am approaching a cut over date to PBX 2020.

I have no doubts that PBX2020 is 99% bug free after my testing.

But I cannot get a Yealink 29g to register.

It must be something simple.

Mark

 

[krzykat]

@redstonemason I can assure you the T29G works fine with it as I've got some. Let's look into where your problem can be.
Are you running local or hosted?
Do you have other phones working?
Are your extensions Chan_SIP or Chan_PJSIP and what port?
What do you have for NAT Mode?

 

[redstonemason]

@redstonemason I can assure you the T29G works fine with it as I've got some. Let's look into where your problem can be.
Are you running local or hosted?
Do you have other phones working?
Are your extensions Chan_SIP or Chan_PJSIP and what port?
What do you have for NAT Mode?

I have running on VULTR hosted. My current production system are running without issues and are extremely reliable and use Yealink phone of different vintages.

The old hosted machines are ruuning Incredible PBX 12.0.74 'Incredible PBX Lean GUI' which is not supported any more.

 

[krzykat]

I have running on VULTR hosted. My current production system are running without issues and are extremely reliable and use Yealink phone of different vintages.

The old hosted machines are ruuning Incredible PBX 12.0.74 'Incredible PBX Lean GUI' which is not supported any more.

So the new 2020 server is hosted on Vultr and other Yealink phone models are working without issue?

 

[redstonemason]

So the new 2020 server is hosted on Vultr and other Yealink phone models are working without issue?

Yes but no look with the very first phone to that I am provisinong as a legacy sip extension.

I think the problem is the changes in the GUI prove the old rev to the new rev has caused me to misconfigure the global sip settings or the global advanced sip setting or the phone extension sip settings.

I have even deleted all the prerouting in the PBX 2020 out of the box iptables setup. I blocked ICMP and I did not see a necessity for the Pre Routing Drop rules.

 

[redstonemason]

Also, I have had no issue setting up a trunk on VOIP.MS. I use them alot. And it came up first time. So calls to a DID pointed at a SIP registration on the PBX2020 are working. The sample IVR gives be the weather for Berverly HillSs

 

[redstonemason]

I found a bug in the GUI. I was using a simple password with numeric and alpha but registrations failed with "wrong password" even though the GUI accepted the password as "so-so".

I am up and running.