I have an issue in a new Voip deployment whereby when a user call forwards their internal phone to an external mobile, the site prefix is being added to the Originating caller ID on the destination mobile phone and trailing digits are stripped.
the site prefix is +43166105
A user outside the company with mobile phone number 06991968XXXX calls an internal extension that is call forwarded to 0664545XXXX, when the call rings on 06664545XXX, the caller ID is shown as +431661056991968, with last 4 digits missing
The site has two voice gateways, GW2 for specific mobile phone calls, and GW1 for regular calls and all other mobile calls, when a user call forwards to a mobile phone that is reachable via GW2, the caller ID is showing correctly (both g/w are connected to different providers)
I have a translation pattern on both g/w that strips the leading zero's of the calling number and also makes sure call type is presented properly to the provider.
Generally, i would be calling the provider, however the site are telling me that this worked OK on the previous PBX based setup.
Here are some relevant pieces of configuration information, and the ISDN debug of an affected call, as you can see, we are providing the correct digits to the provider, yet we always see the prefix regardless
I have tried changing the numbering type in the translation pattern from any to unknown and it has the effect of then showing no digits of the Caller ID, it will just show the prefix number.
trunk group A1_Telekom carrier-id Vienna_A1_Telekom description Vienna_PSTN_Trunks hunt-scheme round-robin both isdn supp-service tbct notify-on-clear translation-profile outgoing OUTBOUND
voice translation-rule 4 rule 1 /^01\(.*\)/ /01\1/ rule 2 /^0/ // rule 3 /^8912$/ /0017275788912/ ! voice translation-rule 5 rule 1 /\+43166105/ /166105/ type any national rule 2 /^000\(.*\)/ /\1/ type any international rule 3 /^00\(.*\)/ /\1/ type any national
voice translation-profile OUTBOUND translate calling 5 translate called 4
dial-peer voice 99 pots trunkgroup A1_Telekom service session destination-pattern 0T fax rate disable direct-inward-dial forward-digits all
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...