Hi,
I am having a strange issue with calls forwarded to my mobile.
My mobile's number (including area code) starts with (something that looks like) 0161/40xxxxxx and so I forward calls to my extension to my mobile at (something that looks like) +4916140xxxxxx.
There is an outbound rule ("Ort") that prepends (something that looks like) +4969 (country code + area code for my city) for any numbers that begin with a digit other than 0 (indicating that no area code was dialed and that it is a local call). This is necessary, as calls to numbers without area code will not succeed.
When my extension is called, the following seems to happen: A forwarding call is generated for 16140xxxxxx (instead of: +4916140xxxxxx) which matches the above mentioned outbound rule and +4969 is prepended. This means that instead of +4916140xxxxxx, 3CX dials +496916140xxxxxx (which is a local number and not my mobile). And the poor owner of that number just called me to complain about her getting my calls for the past three weeks.
Now, I have no idea why that would happen, but I did find this in the 3CX activiy log:
So, for some reason, 3CX seems to drop +49 from my forwarding number and then treats it as a local number and adds the local area code.
Any ideas why that would be?
I have set up no (explicit) rule that would strip "+49" from any numbers. And even if, once one rule matches, from what I understand, no further rules are applied. So my rule to prepend "+4969" would not be applied, if another rule had stripped "+49". Is there maybe an implicit rules that strips "+49" after which my explicit rule still would be applied?
Many thanks in advance!
I am having a strange issue with calls forwarded to my mobile.
My mobile's number (including area code) starts with (something that looks like) 0161/40xxxxxx and so I forward calls to my extension to my mobile at (something that looks like) +4916140xxxxxx.
There is an outbound rule ("Ort") that prepends (something that looks like) +4969 (country code + area code for my city) for any numbers that begin with a digit other than 0 (indicating that no area code was dialed and that it is a local call). This is necessary, as calls to numbers without area code will not succeed.
When my extension is called, the following seems to happen: A forwarding call is generated for 16140xxxxxx (instead of: +4916140xxxxxx) which matches the above mentioned outbound rule and +4969 is prepended. This means that instead of +4916140xxxxxx, 3CX dials +496916140xxxxxx (which is a local number and not my mobile). And the poor owner of that number just called me to complain about her getting my calls for the past three weeks.
Now, I have no idea why that would happen, but I did find this in the 3CX activiy log:
| 03/09/2021 10:48:29 AM - [CM503004]: Call(C:10): Route 1: from L:10.1[Extn:11] to T:Line:10000>>+496916140xxxxxx@[Dev:sip:[email protected]-online.de;transport=TCP] |
| 03/09/2021 10:48:29 AM - Call(C:10): Call from Extn:11 to +4916140xxxxxx matches outbound rule 'Ort' |
| 03/09/2021 10:48:29 AM - [Flow] Call(C:10): has built target endpoint: Out#:>>Rule{Ort}>>16140xxxxxx for call from L:10.1[Extn:11] |
| 03/09/2021 10:48:29 AM - [Flow] Target endpoint for +4916140xxxxxx is Out#:>>Rule{Ort}>>16140xxxxxx |
| 03/09/2021 10:48:29 AM - [CM503010]: Call(C:10): Making route(s) from Extn:11 to <sip:[email protected]:5060/UDP> |
So, for some reason, 3CX seems to drop +49 from my forwarding number and then treats it as a local number and adds the local area code.
Any ideas why that would be?
I have set up no (explicit) rule that would strip "+49" from any numbers. And even if, once one rule matches, from what I understand, no further rules are applied. So my rule to prepend "+4969" would not be applied, if another rule had stripped "+49". Is there maybe an implicit rules that strips "+49" after which my explicit rule still would be applied?
Many thanks in advance!
