Update 6 Beta Available Now

[MHedish]

I seem to have found a bug with the latest SMS change. When I initiate an SMS, I do indeed get the prompt to select which number I'd like to use, but one of them is incorrect.

I have a DID assigned to my extension and I'm also part of a ring group which is routed to based on an inbound CID rule. The DID is correct and works fine. Update 6 is reading the incoming call routing for the CID for that group and presenting it as a DID.

That number is not one of my DIDs nor is it assigned to the trunk. Seems 3CX is reading the DID and any CID assigned via routing to the extension as if it were an SMS enabled DID.

---

---

---

Obviously, the CID for the ring group can't send an SMS message. It seems should validate the numbers it sees for the extension against the list of DIDs assigned to the trunk.

 

[Soli]

but my pbx is on premise and the trunk is gray out

 

[CallingFromMars]

Hi.
What i missing, is the possibility to upload a Backup over the M.C. to activated it later.
What happend a few days before:
I customer installed the 3CX new, and the Backup what i has in the PC was newer then the Version of the .iso, so he can't install the Backup. so he used an old one to go further, but now, he can't install the Backup which was made from the latest Version.
So i helped him to get the newest Backup over scp the the Linux path where the local Backups are stored. But if we had on upload Button on the Gui, it's much more easier to do this.

Bye
Timm

Totally, agree with that. It would be nice to have!
Also the option to also export/import outbound rules as csv (like we have it for inbound rules, or users) would be great.
Also importing call log as csv, as we can already export it.
Maybe even easy to implement.

 

[YiannisH_3CX]

I seem to have found a bug with the latest SMS change. When I initiate an SMS, I do indeed get the prompt to select which number I'd like to use, but one of them is incorrect.

I have a DID assigned to my extension and I'm also part of a ring group which is routed to based on an inbound CID rule. The DID is correct and works fine. Update 6 is reading the incoming call routing for the CID for that group and presenting it as a DID.

That number is not one of my DIDs nor is it assigned to the trunk. Seems 3CX is reading the DID and any CID assigned via routing to the extension as if it were an SMS enabled DID.

Hi @MHedish

Thank you for reporting. We have actually identified the issue and we will fix if for the final. You are correct in that CIDs should not appear as available SMS numbers

 

[Soli]

I added the Twilio SMS but still cant send via the webclient their is no option to send SMS like before.

one more thing i notice is that i cant see the agent outgoing calls anymore in panel (I'm the manager of curse)

 

[JohnS_3CX]

I added the Twilio SMS but still cant send via the webclient their is no option to send SMS like before.

one more thing i notice is that i cant see the agent outgoing calls anymore in panel (I'm the manager of curse)

To be able to send, your twilio number needs to be routed to your extension somehow.

Either directly or by being part of a queue / ring group that is the destination of the number.

one more thing i notice is that i cant see the agent outgoing calls anymore in panel (I'm the manager of curse)

Are you a group manager in the same group as the person making the call? Or are you a manager of another group?

 

[Soli]

I'm the manager of the queue the agent called from

 

[JohnS_3CX]

I'm the manager of the queue the agent called from

But as you said before, you could not see the outbound calls of the users (so the queue is not related at all).

What I meant is to check your user Groups (not queues or ring groups).



You will not see the outbound calls of users belonging to "Sales Group" if you are a manager in "Finance Group" for example.

 

[Yuto Utsumi]

Is there any relief for users who use 0XX extensions?

At least allow existing users to add 0XX extensions

It is difficult for users who use it to change numbering plans.

 

[YiannisH_3CX]

Is there any relief for users who use 0XX extensions?

At least allow existing users to add 0XX extensions

It is difficult for users who use it to change numbering plans.

Unfortunately you will not be able to add additional 0XX extensions but the ones you already have will continue working as before.

 

[N_G]

Just to let everyone know that we have developed a new headset integration which will mean that in update 6/7 there will be a universal headset driver which will work with EPOS and Plantronics headsets as well.

 

[Evolute IT]

Just to let everyone know that we have developed a new headset integration which will mean that in update 6/7 there will be a universal headset driver which will work with EPOS and Plantronics headsets as well.

Neat!

 

[timmbo]

Hi.

What is the reason, why i can't add more 0XX Extensions?

Bye
Timm

 

[davide.bonavita]

Hi guys, it's weird but I can't see the DHCP Option 66 support being removed and re-added in the change log? Is there any other fix or update missing?

 

[PDSS]

Is there a way to change the extension number starting range off 100? In New Zealand there are a lot of 3 digit telco services in the 100 range and our emergency number is 111.

Thanks.

Our best practice guideline is to start extensions from 200. It leaves us with under 200 to make dummy extensions and avoid users to have nummers in the 1xx range. As we, in Belgium, are using 100, 101, 107, 112, ... as priority nummers.
I hope this might help you.

 

[Guillaume Bourgeois]

Hi 3CX Team,
Is it planned to allow calls to be routed to a "group" according to the choice made in an IVR ?

Here is a scenario we encounter ;
The customer has only one DID / one IVR , but wants to manage the schedule according to the department (group).

With testing systems (not production system), I tried directing the IVR option to an new "extension" (Example : 1002 ) that is configured to forward its all calls to a extensions group ( example: GRP0000 ) but it does not work, the caller remains "on hold" and is never connected. ( The caller hears music on hold until they hang up ).
But if I call the extension 1002 with other internal extension, It works correctly, the call is correctly forwarded to extensions group GRP0000 .

If an "internal extension" calls the IVR and chooses option to be routed to extension 1002 (configured to forward to GRP0000 ), it also remains on hold without reaching a destination (GRP0000).

So I conclude that IVRs are not allowed to route calls to the "group destination" extension ( GRP**** ).

Question :

Will you provide a solution for those who wish to manage the schedule according to a department (group of extensions), who have only one DID (Route on an IVR) and who wish to be able to take advantage of the new call routing features towards " extensions group"?
Are there plans to add "action" for routing to a "Group of Extensions" from IVRs ? ( As proposed in inbound rules actions ) or other solution ?

Just to avoid misunderstanding, this is not a suggestion (idea), it is a matter of what is planned by the 3CX team.
I am aware that this page is not intended to share ideas .








Respectfully,

 

[oberserver_at]

hi,
we are currently testing the new beta, a for many of our small costumers its great, the can use a router phone now instead raspi.
The thing is, i dont find a way to select the router phone sbc for dect and ata.
Also i dont understand how to provision these device classes realiabe without raspi sbc

 

[N_G]

You can provision a DECT phone or ATA just have to give the routerphone IP as the proxy.... Right now you have to do it manual, soon the webclient will allow you to configure DECT phones as well.

 

[illcsales]

In the Web client under Users, IP Phone, IP Phone Console, Web Console URL, the full username and password is exposed should this not be obscured like other password fields or removed, those whom need it should know how to get to the device without spelling it out?

 

[jvivona]

anyone else seeing errors trying to install the beta over an SP5 instance? we're looking at our test system and upgraded it and getting these kinds of errors. Our next move is to take a backup, do a purge of 3cx and install the beta & restore the data. But just wanted to see if there was something I'm missing.

Updating from Version 18.0.5.418
Loading global scripts...
Loading instance scripts...
Loading instances...
CurrentDbVersion=542
Updating global DB tables...
Applying script for all instance tables
Loading instance parameters from phonesystem_mastertable
Updating instance DB tables...
Replacing parameters
Npgsql.PostgresException (0x80004005): 42601: syntax error at end of input
   at Npgsql.NpgsqlConnector.<ReadMessage>g__ReadMessageLong|194_0(NpgsqlConnector connector, Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult()
   at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteScalar(Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteScalar()
   at Updater2Db.UpdateInfoExtractor.ExecuteScript(String sqlQuery, String transactionName, Exception& err)
  Exception data:
    Severity: ERROR
    SqlState: 42601
    MessageText: syntax error at end of input
    Position: 36
    File: scan.l
    Line: 1119