During my last project I had to work on a CUCM already configured for a few German SIP providers. All outbound calls where using E.164 addressing. It seemed a bit complex at first sight but was pretty easy to setup in the end (so this is not my idea, I just used the method for the Dutch branche).
First create a partition for your SIP-trunk, lets call it PT_NL_PSTN. Create a Route pattern \+.! and put this in the PT_NL_PSTN partition. Add your gateway or trunk to this pattern. Create a CSS containing only the PSTN-partition. In this case we name is CSS_NL_E164.
Create two Translation Patterns 00.! and 000.!. The first one is for national numbers, the second one is for international numbers (the first zero is the outside prefix). This is a Translation Pattern for phones using their External Phone Mask as their Calling Party number.
The route pattern is placed in a seperate partition based on the calling rules for outside calls. In this case the calling party number should be a DDI. This partition is added to the Line or Device CSS (depening on the setup).
The 00 is discarded and a +31 is added to the Called Party number. The Translation Pattern uses the CSS_NL_E164 to reach the Route Pattern needed to to get the call outside the building. In the Translation Pattern 000.! the prefix is simply a +.
This is the flow: Caller A calls B. B is in Amsterdam and has number 020-1234567. A has DDI number 085-7654321.
- Caller A, calls 00201234567
- Translation Pattern 00.! is matched because partition PT_NL_DDI is in his line CSS
- The prefix is discarded
- +31 is added to the number
- Route pattern \+.! is matched because it is in a partition in de Calling Search Space CSS_NL_E164.
- The Call is routed towards the voice gateway and the SIP provider.
The SIP provider they are using is only allowing an E.164 address for the Called Party, not the Calling Party. So the ANI and DNIS look like this:
ANI : 0857654321
DNIS : +31201234567
No comments:
Post a Comment