NethVoice Reports Prefix for US

Shadowfire · September 27, 2024, 11:31pm

I am currently trying to run NethVoice. My challenge is what should be the correct prefix for the United States. I have tried a number of prefix that seem that they should work.

I have read through the documentation

https://docs.nethserver.org/projects/ns8/en/latest/nethvoice.html#configuration

the NethVoice docs (config) says the following -

Reports Prefix: Insert the international telephone prefix to be considered local in the reporting system.

And the Reports Prefix has a (i) help/hint that says -the format should be either “00**” or “+**”

So based off the international prefixes I would normal setup, I have tried the following to enter -

examples -

+1
+011
+001
+00

**1
**011
**001
**00

But when I try to put in what I believe should be the prefix, it says invalid format, as you can see in the screenshot below -

Can anyone help get this on the right track.

Thanks
-SF-

dnutan · September 28, 2024, 1:36am

according to the regex pattern, it only allows:
exactly 00 and two more digits
or
exactly + and two digits.

github.com

nethesis/ns8-nethvoice/blob/75c0200de6158cc6225e7904cb6e6afc860dc07f/ui/src/views/Settings.vue#L643


      
          if (!this.form.user_domain) {
            this.error.user_domain = this.$t("error.required");
            isValidationOk = false;
          }
          
          if (!this.form.timezone) {
            this.error.timezone = this.$t("error.required");
            isValidationOk = false;
          }
          
          const reportsPrefixRegex = /^(00\d{2}|\+\d{2})$/;
          if (!reportsPrefixRegex.test(this.form.reports_international_prefix)) {
            this.error.reports_international_prefix = this.$t(
              "error.reports_prefix_invalid"
            );
            isValidationOk = false;
          }
          
          if (
            this.form.nethvoice_host === this.form.nethcti_ui_host &&
            this.form.nethvoice_host !== ""

I think that works for Europe, Asia, Africa…
while USA (and Canada) use 011 or +1

Bug ?

Shadowfire · September 28, 2024, 1:52am

A bug? Maybe… Other countries use between 1, 2, and 3 digits as well, or maybe there is a different standard NethVoice is using, and they can let us know that standard and what the US Prefix is.

For the references that I can find for International Prefixes, see examples websites below -

https://wikitravel.org/en/International_dialling_prefix

List of international call prefixes - Wikipedia

What is the calling code for the United States? Making your phone call - Wise

https://countrycode.org/

United States Country Code 1 Country Code US

US Phone Number Format Examples with Country Code

List of country calling codes – Travel guide at Wikivoyage

https://www.nationsonline.org/oneworld/international-calling-codes.htm

List of country calling telephone number prefixes

https://www.allareacodes.com/international_dialing_codes.htm

@davidep @Amygos @federico.ballarini

LayLow · September 28, 2024, 2:25am

+01 according to the Nethvoice logic, BUT this is not according to international standards, ITU and reporting (or exports for further processing) will fail for Asterisk adheres to E164 standards. This is a bug and should be reported as such. It should be either “00” or “+” or “” (nothing) and then the E164 country dialing code, so the total length may vary a lot.

https://www.itu.int/oth/t0202.aspx?parent=t0202

The hover tip in the settings is obviously not correct in this case.

I am not sure which for which reporting this is intended, for the reporting module (other then default CDR’s) is a commercial module and can not be tested here. In case it IS intended for the reporting mdule, than it lives its own life, outside of any E164 standards. (which is not a good thing for obvious reasons)

JFYI, all major vendors (Avaya, Cisco, 3CX, Panasonic, Siemens, Microsoft etc) implement the dialing plan logic according E164 guarded by the ITU.

I suggest NethVoiceand NethVoice-Proxy follow strict E164 standards to be fully compliant and compatible.

Shadowfire · September 28, 2024, 3:02am

E.164 Infor on it -

I agree. It seems like E.164 standards would be an easy pick since most phone equipment, software and countries adhere to that standard. Of course, if they need to do another standard as well, then just build both of them to be used and make it selectable and recommend E164 as default.

Hope we can get more info on the thought process of why they are not using E.164 standard.

Btw, I did try to use +01 and it didn’t work. I will look further at it. Thanks for the information and the followups. It’s Helpful.

LayLow · September 28, 2024, 3:12am

I was able to use +01 and save it. No testing tho.

oneitonitram · September 28, 2024, 4:45pm

I also tried +254 for Kenya and it failed

LayLow · September 28, 2024, 5:17pm

Can you show how you tested pls?

LayLow · September 28, 2024, 7:15pm

I see, you can not save it at all in the first plce due to the format restrictions.

NethVoice needs to be adapted to Intl usage, it is now very Italian oriented. Inlcuded SIP trunk providers, all Italy oriented. And looking at the Nethserver audience on the global deployment map it surprises me.

I also would like to point out previous questions:

Stll0 · September 30, 2024, 7:39am

It’s a bug NethVoice report prefix validator doesn't allow for 3 digits prefixes · Issue #7043 · NethServer/dev · GitHub

here a workaround:

Use a 2 digits prefix
change the value of REPORTS_INTERNATIONAL_PREFIX variable in module environment file /home/nethvoiceX/.config/state/environment
restart report-api container systemctl --user restart reports-api

oneitonitram · October 1, 2024, 5:52am

While this technically works, it leaves alot of grey areas for alot of users.

Could you try to dumb it down abit more, in the sense of not assuming alot

Stll0 · October 1, 2024, 6:45am

Fix is merged, next testing package and next release will have it