Issue with Fanvil X3U "auto send" after dialing number

[dottydot]

Im new to 3CX and IP phones in general.
I have a test bench with 3CX running on AWS EC2, a Twillio SIP Trunk, the SBC on premises running on Debian, and 4 Fanvil X3U.
So far my tests are going well but it annoys me that I must hit "#", or hit the soft-button "dial" after dialing phones or extensions for the call to actually go out to the PBX.
How can I configure "auto-send"?
On my old system I just pick the headset or open the speaker, dial 124 and a second later extension 124 rings.
Same with external numbers, I dial 4073426334 and a second later it gets dialed, same with International numbers, etc.

On Fanvil phones I have to actually press "dial" or hit "#" so the call is sent to the server (screenshot attached here).

There is a config page on the phone itself via web interface where I can sort of set this up, but I would hate to do it on every phone.
There has to be a better way.




Dotty

 

[ChrisC_3CX]

As a first note, I'm pretty sure that you can dial the number and then simply pick-up the handset or press the speaker button for the call to automatically go through, without the need of pressing dial or #.

There is a config page on the phone itself via web interface where I can sort of set this up, but I would hate to do it on every phone.
There has to be a better way.

Regarding the settings you mentioned, if you are referring to "Press # to invoke dialing" or "Send after" do bear in mind that you cannot configure these two settings via 3CX nor do we set them via our template. That said, the only way I can think of is to use a custom template which you will have to modify to initialize these settings with the desired values. You would then have to configure all X3U devices to use that template which kind of beats the purpose since you didn't want to configure every phone in the first place. On top of this, using custom templates will render the particular configuration unsupported by 3CX so I would not actually recommend going down this road.

 

[dottydot]

Yes, I dont want to use Custom Templates either.
You are right, if I input the number and then lift the headset then it gets dialed. Same if I input the number and then press "speakerphone" , it also get dialed.
But thats not the way the customer are used to, they are used to lift the headset, or press speakerphone, wait for dial tone, input the number and wait a second or two so the number gets dialed.
Im surprise how I cannot find references to that issue on these forums. Perhaps im doing something wrong and I dont get the expected results. I cant believe how this behavior Im having with these phones can be normal.

 

[ChrisC_3CX]

I cant believe how this behavior Im having with these phones can be normal.

I just tested this on an X4U and I am getting the same behavior you are describing so you might want to check Fanvil's documentation to see if there are any settings you could set to get the desired behavior. If you do find a setting that does what you need, you would then have to re-provision the device from 3CX to see if the setting gets overwritten by our template, if it does not, you could manually set it on every phone and it should remain. I do have to warn you though, that manual configuration on IP Phones is not recommended and will render that IP Phone's configuration unsupported. I honestly think that it would be best to simply let the customer get accustomed to the new behavior as to keep the configuration as "clean" as possible.

 

[dottydot]

I just tested this on an X4U and I am getting the same behavior you are describing so you might want to check Fanvil's documentation to see if there are any settings you could set to get the desired behavior. If you do find a setting that does what you need, you would then have to re-provision the device from 3CX to see if the setting gets overwritten by our template, if it does not, you could manually set it on every phone and it should remain. I do have to warn you though, that manual configuration on IP Phones is not recommended and will render that IP Phone's configuration unsupported. I honestly think that it would be best to simply let the customer get accustomed to the new behavior as to keep the configuration as "clean" as possible.

They will not be at all that happy. They are not that big, just 42 extensions, but that might be a deal breaker for them. I just wrote to Fanvil to see if there is something that can be done, but I understand your point about hte phones not being supported. But I think that behavior should be supported/included in the custom 3CX firmware they release.

 

[leejor]

This document applies to various Fanvil models, yours may only have limited support, for an internal dialplan.

https://www.fanvil.com/Uploads/Temp/download/20191225/5e0335d8db615.pdf

Some sets allow you to create rules for every possible combination of digits dialled. Many allow those digits to be modified as well, if required. This way the set knows that you have finished (a match has been found), and will then send the digits to the SIP server.

Without a phone, with a detailed dialplan, you will have to carry on as-is. Perhaps, if some additional sets are required, in the future, this will be a consideration when making a purchase.

 

[dottydot]

This document applies to various Fanvil models, yours may only have limited support, for an internal dialplan.

https://www.fanvil.com/Uploads/Temp/download/20191225/5e0335d8db615.pdf

Some sets allow you to create rules for every possible combination of digits dialled. Many allow those digits to be modified as well, if required. This way the set knows that you have finished (a match has been found), and will then send the digits to the SIP server.

Without a phone, with a detailed dialplan, you will have to carry on as-is. Perhaps, if some additional sets are required, in the future, this will be a consideration when making a purchase.

Thanks for the doc, Im reading now.

 

[dottydot]

I just tested this on an X4U and I am getting the same behavior you are describing so you might want to check Fanvil's documentation to see if there are any settings you could set to get the desired behavior. If you do find a setting that does what you need, you would then have to re-provision the device from 3CX to see if the setting gets overwritten by our template, if it does not, you could manually set it on every phone and it should remain. I do have to warn you though, that manual configuration on IP Phones is not recommended and will render that IP Phone's configuration unsupported. I honestly think that it would be best to simply let the customer get accustomed to the new behavior as to keep the configuration as "clean" as possible.

Chris

Do I render my phones 'unsupported' if I use custom templates inside 3CX? If not, how do I set parameters for the dial plan? I see them on the device's web GUI but I cant find them on the template inside 3CX.

 

[ChrisC_3CX]

Do I render my phones 'unsupported' if I use custom templates inside 3CX?

Yes, they will be considered unsupported if configured via a custom template.

By the way, I ran a few more tests and can confirm that the call should go through automatically if you:

1. Pickup the handset or open speaker.
2. Dial the number only.
3. Wait for the time specified in the "Send after" field.

What might be causing some confusion may be the fact that the "Send after" default value is set to something like 10 seconds (as I can confirm applies for the X4U) meaning the user has to wait for 10 seconds before the number gets dialed automatically. Since we do not set that value in the template, it will not get overwritten so you could, as you have already mentioned, manually edit that timeout on every phone and the setting will stay as long as the phone does not get reset. I know you said you do not want to make changes for every phone individually but I think that this would be the best option for this scenario.