BCM400 v3.7 Routing with multiple PRI

[jeffreyn]

I'm trying to connect our BCM400 to an Asterisk system via PRI, with the end goal of integrating Microsoft OCS/Lync through the Asterisk system.

The BCM started with 1 PRI (PRI-A on bus 7) that handled all of our incoming/outgoing calls. I added an additional DTM card on bus 6 (PRI-B) and connected that to an Asterisk system with a Digium card. I am able to make/recieve calls between BCM and Asterisk internal extensions, but when I try to dial out to the PSTN (via PRI-A) from Asterisk, the BCM always interprets it only as an incoming call and routes it based on the last 3 digits (we use 3 digit extensions).

Is it possible to call out PRI-A from calls originating on PRI-B? If so, can anyone help me figure out what I'm missing in the configuration?

Here is some info that I think is relevant:
-- All lines from both PRIs are assigned to Remote Package 01, which contains Pool A (VoIP lines to two remote BCM50s), Pool PRI-A, and Pool PRI-B.
-- Trying to use the existing route out of the BCM to PSTN, which is standard dial '9' + number, but looks like the BCM isn't using the Destination Codes for the calls incoming from PRI-B.

Thanks!
Jeff

 

[vztech]

couldn't you just bypass the Asterisk box and have the PRI or SIP trunking teminate into OCS ?

Strange that the BCM would pick the last 3 digits.

I think what your trying to do should work with some tuning.

What about setting it up as private and not public?

check this thread

thread1361-1563871


It's only dialtone!!!

 

[jeffreyn]

Hi vztech,

OCS/Lync needs to connect with SIP over TCP which I don't believe the BCM400 supports.

For the private/public thing are you talking about for the whole PRI? I was wondering if there was some setting to classify the trunk as private/public but didn't find anything. It looks like right now the BCM is treating both PRI-A and PRI-B the same way, reading just the last three digits on incoming calls through their respective links.

I did try to connect the BCM and Asterisk via H.323 trunks and that kind of worked (calls would connect but disconnect after 5-10 seconds), but made our BCM unstable. Eventually IP phones/services would start acting funny and would need a BCM reboot to start working properly again. External calling from Asterisk -> BCM out the PRI did work via the IP trunk, and it does work from the two remote BCM50s connected via H.323 also.