call routing with ISDN and SIP trunk in 1 gateway

[HubertMaier]

Hello,

we have the following setup. The CUCM connect via SIP trunk to a Cisco 2921. The 2921 have a SIP trunk to a phone provider and BRI interfaces for ISDN connections. The SIP trunk provide the phone numbers for office 1, the BRI interfaces the phone numbers for office 2.

Incoming calls working fine, the problem are outgoing calls. How can I define the outgoing trunk/interface by source? The phone numbers in office 1 starting all with 0691234567 + 1 digit for the extension. The phone numbers in office 2 starting all with 073112345 + 2 digits for the extension. Currently the Router use 1 time the SIP trunk, 1 time the BRI interfaces.

If it is not possible to do that in the router by phone number, is it possible to connect from the CUCM 2 times to the router, over different ports or something else and bind the first trunk to the SIP trunk and the second trunk to the BRI interfaces?

Andreas

[Aaron Harrison]

Hi

Two options:

Option 1: Register the BRI as MGCP to CUCM, leaving the SIP trunk routing as is. This way you can sent calls from Ofifce 2 (through use of seperate CSS,Parititon, Route Pattern/RG/RLs) to the MGCP BRI 'gateawy'. Office 1 calls can be sent to the SIP trunk, and will use the non-MGCP bound destinations (dial peers pointing to SIP).

Option 2: Set up separate CSS/Pt/RP/RL/RGs for office 2. Prefix calls sent to the gateway from office 1 with a particular prefix, and those from office 2 with a different prefix (configuring the CUCM RGs or RPs to prefix the digits, not making the users dial them).  On the gateway, configure the peers for the BRI with the office 2 prefix, and the peers for SIP with the office 1 prefix.

Regards

Aaron

[HubertMaier]

Hi,

thanks

I tried the second option, how can I configure the dial-peer with a prefix of the source of the call?

I found in the documentation only the destination-pattern command for a outbound dial-peer.

Regards

Andreas

[Aaron Harrison · Accepted solution]

Hi

If you set a prefix on CUCM, e.g. 979, then on your destination-pattern use 'destination-pattern 979T' for example.

It's not a seperate command, just use of prefixes in the same ones..

Aaron

[HubertMaier]

Hi,

thanks for help. The system is working perfect.

Andreas

[Aaron Harrison]

Great news :-)