Internal calling does not work when upgrading to v20

Status
Not open for further replies.

adventure

Free User
Basic Certified
Joined
Apr 9, 2019
Messages
10
Reaction score
1
Hello everybody

After I migrated 3CX to version v20, some extensions cannot connect to each other.

Outbound calls work normally, but extension-to-extension connection does not work.

Call from 102 to 101 work.
Call from 101 to 102 not work. (shows message bellow)

There was no user or outbound rule found for the number xxxxxxxxxxx that Ext.101 dialed.

Does anyone have any idea what it is?

Thanks
 
I don't understand why shows a mobile number in the message if I'm calling an internal extension number.
 
is that extension set to forward to or “call my mobile?”
 
Is there any exception configured on the extension?
What is the status of the extensions?
What are the forwarding rules of the extension?
 
Hello

@stevelITS no, the extension does not have forward set. I created two extensions 103 and 104, both go directly to voicemail. But not show any error message.

@TheodorosG_3CX
1 - no, I created two new extensions without any extra configurations.
2 - all are available.
3 - does not have any forwarding specific for extensions.

Another info:

If i'm logged with extension 103 and go to panel to see all team I can see 101, 301, but not 104. The same occurs with 104, I can see 101 and 301, but not 103.

All extensions are in the same department Default.

Thank you
 
Have you allowed notifications from the web client's as per this forum post?
 
Hello Theodoros and Stevel sorry for this post. When I updated to v20 all mobile devices with 3cx client goed down. I dont verified this...

When I tried to call then all extensions are offline and the call goes directly to voicemail.

I reprovised all mobiles devices and all calls works well...
 
If you are referring to using webclients, then in version 20, the webclients use push, which requires them to be enabled for notifications. You can do this with either of the 3 options below:

1. Press the bell icon at the top left of the webclients, and allow the notifications that appear unregistered.

2. You can also check from the browser settings by clicking the icon below next to the URL

attachment


3. Try this: If you have missed the bell icon, you can add it manually by pasting the URL below into the browser.

chrome://settings/content/notifications?search=notification
attachment


In the section above, add the URL to the web client. This will then show the users as registered.
 
  • Like
Reactions: TheodorosG_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,953
Messages
589,910
Members
164,845
Latest member
tdzski5