Call Limitations ---------------- This section explains the limitations and observations in the looping dial plan with the proposed solutions. .. tabularcolumns:: |p{4cm}|p{7cm}|p{4cm}| +----------------------------+----------------------------------------------------+---------------------------------------------+ | Call Type | Observation | Proposed Solution | +============================+====================================================+=============================================+ | Incoming calls from PSTN | For any such call types or features, creating an | Insert a dummy PAI in Cisco Unified CM with | | forwarded via: | outbound Call Leg based on the restricted A - | a Lua script. | | | | | | * Call Forward All back to | Number by Cisco Unified CM, fails if the | * INBOUND: If there is no | | the PSTN | incoming calling party is anonymous. | P-Asserted-Identity (PAID), set the | | * Call Forward All, No | In this scenario, the calling party number does | PAID to and | | Answer, ...To VoiceMail | not have a PAI field and the From field is set to | set the privacy to restrict the number. | | * SNR | "anonymous" with no digits in the incoming | * OUTBOUND: If the PAID is | | * Dial Via Office | CLIR PSTN call. For security purposes, HCS | , remove | | | prefixes a dial plan pattern (for example, \+*\+*) | the PAID | | | to the incoming calling party number to | | | | "anonymous". | | | | | | | | If the Cisco Unified CM pattern does not have | | | | the capability of that matching letter (dial plan | | | | pattern), the call fails. Also, Cisco Unified CM | | | | cannot match the dial plan pattern (for example, | | | | \+*\+*) because the calling party number | | | | ("\+*\+*anonymous") is treated as enbloc by Cisco | | | | Unified CM. | | | | | | +----------------------------+----------------------------------------------------+---------------------------------------------+