Problem adding a new extension

[Bert1]

OK, I'm new to 3CX so I am most likely doing something very simple incorrectly but I can't get this thing to work at all. Every time I add a user, the Extensions page shows the user with a big red circle on the left which, I assume, means that the account is not properly configured. If I hover my cursor over the red "!" beside the account name, it tells me that the password must be at least 10 characters long with one capital, one lower case and one digit in it. Yet, when creating the account, the system provides a password (where it gets it from, I don't know) but, while it will allow me to change the password, the new password never sticks. Every time I go into the extension details, it has the same, incorrect, password.

So, am I correct in assuming that the red circle means that the extension is not operative? If yes, what do I need to do to get it operational?

On another note, is there anything special I have to do to get a Polycom VVX401 to play nice with a 3CX or is the problem I am having with it related to the extension issue mentioned above?

Thanks

Bert

 

[SweetAction]

Bert1,
The ! is a warning to indicate the password chosen is insecure.
Try making an extension with the default generated password - you should have no ! next to it.
Then see if you can provision the phone before changing the passwords.

The only password you should need to change is the webclient password - the sip credentials should not need to be shared or changed.

 

[Saqqara]

Info on setting up the phone https://www.3cx.com/sip-phones/polycom-vvx/

Are you using windows or Debian version ?

Is the 3cx hosted in the cloud, or local ?

 

[Bert1]

Info on setting up the phone https://www.3cx.com/sip-phones/polycom-vvx/

Are you using windows or Debian version ?

Is the 3cx hosted in the cloud, or local ?

I guess I left out some info

I have a locally installed copy of 3CX running on a Windows box in a Windows environment.

I have followed the info on that link already but I still can't get it to work. I can assign the phone to an extension but, if I call the DID, I get voicemail and the 3CX log simply shows that an incoming call went unanswered. The phone doesn't ring. If I try to dial out, I simply get a fast busy.

I also can't connect using either the web client or the soft phone. I assume that that is a direct result of the extension provisioning problem I am having so I am trying to focus on that first.

Bert

 

[nub]

I guess I left out some info

I have a locally installed copy of 3CX running on a Windows box in a Windows environment.

I have followed the info on that link already but I still can't get it to work. I can assign the phone to an extension but, if I call the DID, I get voicemail and the 3CX log simply shows that an incoming call went unanswered. The phone doesn't ring. If I try to dial out, I simply get a fast busy.

I also can't connect using either the web client or the soft phone. I assume that that is a direct result of the extension provisioning problem I am having so I am trying to focus on that first.

Bert

you need some incoming and outgoing rules.

https://www.3cx.com/docs/manual/inbound-did-call-routing/

 

[Bert1]

you need some incoming and outgoing rules.

https://www.3cx.com/docs/manual/inbound-did-call-routing/

Inbound and outbound rules already defined. Incoming calls go to voicemail, the extensions (VVX or softphones) never ring and the call shows up in my 3CX log. Since that calls go to the correct voicemail, is it safe to assume that the inbound rules, at least, must be configured correctly?

Back to my original question, am I correct in assuming that a red dot on the left end of an extension entry is an indication of an error in configuration?

Bert

 

[Saqqara]

I would select the phone, under Extension and click on 'Regenerate' button at the top - this will reset passwords, etc

As long as you have dhcp option 66 configured, reboot the phone and it should pickup the changes

If everything is OK, does the extension have a green icon against the extension within Extensions

 

[AWS2P]

if you call internally between two extensions is the phone ringing?

 

[Bert1]

I would select the phone, under Extension and click on 'Regenerate' button at the top - this will reset passwords, etc

As long as you have dhcp option 66 configured, reboot the phone and it should pickup the changes

If everything is OK, does the extension have a green icon against the extension within Extensions

I went back to verify that I had the correct firmware version for the VVX. The website says 5.6 but doesn't say if that is the only version that will work or if it is the earliest version that will work. My phone has version 6.1. When I reboot it now, though, I get a "Provisioning Failed" message. The red dot is still on the extension and outgoing calls result in a fast busy.

Bert

 

[Bert1]

if you call internally between two extensions is the phone ringing?

I currently only have one extension. I did have two when I started this but I couldn't get rid of the red dot on either and I deleted one. However, I was unable to make an extension to extension call when I had the two of them.

Bert

 

[JohnS_3CX]

Hi Bert,

Please state your exact PBX version and what browser you were using for this operation.

 

[SweetAction]

red dot means extension is not registered. Under the phones tab, you likely don't have any entries, or the entry is in bold.

The phone will need to be registered before an incoming call will ring

 

[Bert1]

Hi Bert,

Please state your exact PBX version and what browser you were using for this operation.

Where do I find the PBX version number? It should be the latest version but I'm not 100% certain.

I have been able to get one extension sort-of working. I abandoned the VVX in order to simplify things a bit and I am using a 3CX Client. It does register (green dot ) but when I try to make a call (external), I get a "Call failed, forbidden" message.

Bert

 

[Bert1]

red dot means extension is not registered. Under the phones tab, you likely don't have any entries, or the entry is in bold.

The phone will need to be registered before an incoming call will ring

I just set up a new client with a softphone and finally got one registered

Bert

 

[Bert1]

Hi Bert,

Please state your exact PBX version and what browser you were using for this operation.

When I check the properties of a sip trunk, what should I see for its Authentication Password? Whenever I go into that page, I see a password that I did not assign and isn't the correct one. I change it and click OK but, when I go back in, it is the old, wrong, one.

Bert

 

[AWS2P]

Your pbx version is in MC , dashboard view , right column

 

[Bert1]

Your pbx version is in MC , dashboard view , right column
View attachment 12266

OK, thanks. I get version 15.5.15502. Updates are set to automatic so I don't know why I am so far behind your example.

I have been able to get one client to register (the other is still failing with a time out) and, after talking with IXICA tech support, I was able to get the working client to make external calls (the IXICA sip trunk requires a custom outbound parameter set but I was not aware of that). Incoming calls are still failing, though.

Bert

 

[AWS2P]

because you are on windows machine, to update V16, you need to do a complete backup, keep the backup outside of 3cx, the deinstall 3cx, DL and install latest V16 and most important:
RESTORE DURING reinstall not after.

This complete process take max 15 minutes

 

[SweetAction]

Also, I don't think Windows 7 is supported for V16, so make sure to be using Windows 8/10 or better yet, switch to the debian version.

For the outbound call and forbidden message, sounds like an outbound rule missing OR your SIP Trunk Provider is rejecting it. Check the logs for more info.

 

[Bert1]

because you are on windows machine, to update V16, you need to do a complete backup, keep the backup outside of 3cx, the deinstall 3cx, DL and install latest V16 and most important:
RESTORE DURING reinstall not after.

This complete process take max 15 minutes

I'll have to do that after I get everything working

Bert