Call Forwarding / Displayed Number on Forwarding target with H.323 Gateway
i´m wondering if there is sort of a simple way to get this working properly.
Germany, variable dial plan, no fixed NANP, and we have ClipNoScreening ;)
We use 0 for getting PSTN-dialing.
We have internal DNs, for example a 6789, 4 Digits. We use external phone number mask on our lines, 123456XXX
Our main number is 0123/456-xxx
When i call outside everything is displayed fine on the called target, +49 123/456789.
When i forward a call on my cellphone, with CFA target of 00111/222333444 (my cellphone example), and an internal colleague from within our office, is calling my office phone, everything is ALSO displayed fine.
Now here comes the BUT:
When someone calls from PSTN on my office-phone, i get displayed on my cellphone the +49 (0) 0xxxxxxxx, which means the caller number PLUS the added 0 from the gateway. Which is completely consequent and correct, since we add them on the gateway, when a call comes in, to be able to just answer directly on the office phone.
The rule on the H323 gateway:
voice translation-profile OUTGOING-VOIP translate calling 1 translate called 2
voice translation-rule 1 rule 1 /^\(.*\)/ /0\1/ type subscriber unknown plan any unknown rule 2 /^\(.*\)/ /00\1/ type national unknown plan any unknown rule 3 /^\(.*\)/ /000\1/ type international unknown plan any unknown ! voice translation-rule 2 rule 6 /4560$/ /6600/ rule 9 /^456\(...\)$/ /6\1/
voice translation-profile OUTGOING-POTS translate calling 3 translate called 4
voice translation-rule 3 rule 1 /^00049/ /0/ type unknown national rule 2 /^0/ // type unknown subscriber rule 3 /^00/ /0/ type unknown national rule 4 /^000/ /00/ type unknown international ! voice translation-rule 4 rule 2 /^00049\(.*$\)/ /\1/ type unknown national rule 3 /^000\(.*$\)/ /\1/ type unknown international rule 4 /^00\(.*$\)/ /\1/ type unknown national rule 5 /^0\(.*$\)/ /\1/ type unknown subscriber
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...