Chrome extension 1.1.0 released

[sbasan]

Done this.
The extension has the dial permission but still only local extensions can be dialed using the dial action button or pressing other extension button.

[nicolas]

So it fails when you try to dial outside numbers? Do you use any module that might affect outbound calling? Does your phone ring when you attempt such a call? or not at all? You can start FOP2 server in debug mode and capture output while you attempt to dial outside numbers via the dialbox.

http://support.asternic.biz/?/selfhelp/view-article/how-to-debug-fop2/10

[sbasan]

Thanks.
looks like the problem is the context.

Dial from fop2 has context: domain.name-ext-local
Has this context works for local numbers dialing to external number with the same context got response:
127.0.0.1 <- Response: Error
127.0.0.1 <- Message: Extension does not exist.

Dialing external numbers use the context: domain.name-from-internal

Why external numbers use local context?
fop2 ver 2.9 use the correct context for external numbers so dialing external numbers worked.

[nicolas]

the context is defined in the buttons configuration, that can be handled either by manual config or via fop2 manager and its backend functions files that can be tweaked if they are not correct. I have no idea nor context about your setup so I cannot answer, just fix your button config definition and you will make it work. This issue is NOT RELATED to the chrome extension at all, it is just a misconfiguration of context in the buttons.

[sbasan]

Changing the context fix the dialing.
Which file I need to change the context so there will be no need to manually update each button?

[nicolas]

Are you using the fop2 manager? What backend? I cannot answer without having this knowledge... most probably you have to modify a functions-xxxx.php file in the fop2 manager, but I cannot tell if you do not tell me your backend.

[mkeuter]

Can it be the Chrome extension strips the leading "+" sign, when dialing international numbers (e.g. +49 40 1234567) ? Also in conjunction with the Dial Prefix in the configuration. That makes it difficult to route the route in Asterisk.

[nicolas]

Why it makes it difficult? + signs are not valid characters for phone dialing, if you need to add that you should do it in your routes, not ask people to dial it. The number matching algorithm strips punctuation, and it does it by design, as 99% of people dialplans will break if you dial + or ( or - or whatever. Numbers should be plain number, then you can use a prefix if you come from the old PBX days where dialplan pattern matching was not really an option.

[mkeuter]

When you activate "Clickable Numbers" then you can dial e.g. phone numbers from websites, which are often listed in international format e.g. "+49 40 123456" without the plus sign this could also be a local number in Hamburg, Germany. In Germany we don't use the NANP (with fixed lengths) but have dynamic length numbers.

Since the Chrome Extension has no conversion rules, the only way is to do the filtering in Asterisk (e. g. "exten => _+ZXXX.,1,NoOp()").

[nicolas]

Unfortunately that cannot be fixed. Punctuation is removed from any clickable number.