When i Call from Handy it always cut the “+” from the Number.
My Context is in all config’s >> from-pstn
It change nothing when it to something else - but i don’t want that it do anything with the countrycode
Is there any way to deactivate the e164 permanently? Or what my options? cause when i want call the missed number - the number doesn’t existes cause the number must be +43650xxxxxxxx but it is displayed as 43650xxxxxxxx
The from-pstn context does not manipulate the CALLERID(number) in any way if “Handy” needs a + at the beginning then do that in the Handy trunk , you would need to prepend + to that trunk definition’s dial pattern
thx for answer but i think u mean other thing.
The Prefix u meant is for DIALING Numbers, but i meant the Incoming Calls on my Extension (Softphone and Hardware-Phone) shows in Display the Incoming Number without the +
In the Red Marked u see what i meant. The Purple marked is another Thing i want see but thats not so important.
Austrian area code 650 is for cell phones, you need to be able to dial 43650XXX. from your VSP, likely you need to add 00 or strip the initial country code if your VSP needs that, you should consult them.
Yes, if you don’t refactor the inbound CID then you get what you get , e164 is not pertinent to from-trunk, it is pertinent if you sent it to from-pstn-e164-us, but you really don’t want to do that because you are in Austria, you can modify [from-pstn-e164-us] to [from-pstn-e164-at] and put it in extensions_custom.conf and use that context for inbound calls, if you do that, then reference :-
First, you need to decide on a number format for your system – users will dial calls in this format, incoming calls will display in this format, and any contact lists in the system or devices will use this format.
Unless you have special requirements, I recommend that you choose one of these:
Scheme A: 01 222 3333 (a number in Vienna); 00 33 1 2222 3333 (a number in Paris)
Scheme B: 43 1 222 3333 (a number in Vienna); 33 1 2222 3333 (a number in Paris)
Scheme A is usually better for businesses that are mostly domestic, because users dial and see numbers in the same format that their home and mobile phones use. If you do a lot of international business or have extensions in multiple countries, scheme B may be more suitable.
For outgoing, your Outbound Routes should recognize numbers in whatever scheme you choose and in most cases not modify them. For each Trunk, the Dialed Number Manipulation Rules should convert your internal format to whatever your provider requires. That way, a route can fail over to a provider that needs a different number format.
On incoming, any trunk that provides the caller ID in a different format should be routed to a context that rewrites the number to your internal format. If you have multiple trunking providers and they use different formats, you may need to create more than one such context.
If you still have trouble, post your desired internal format, what your trunking provider supplies for caller ID, present code for your context and what goes wrong; we can perhaps help you debug it.