External forwarding on the Tie line

[mt6322]

I have an Meridian Option 81C Suc 3.0 on one site connected via PRI tie line to a Cisco Call manager using QSIG on another site. My problem is when an extension on the Cisco Call Manager is forwarded to an external number, the caller from the Meridian PBX side hears a busy signal. The tie line call will go through only when the Cisco extension is forwarded internally.
Note: PBX extensions are set to UNR, NCOS 5, FTTU, TGAR blanked. CDB Net Data TRNX and EXTT to yes, RDR data and FTR data=Yes.

External forwarding works on the Cisco side works except calls from the tie line from the Meridian PBX side.

Appreciate your help. Thanks in advance.

 

[Reusser]

So caller dials number and through M1 PBX to Cisco and then back out Cisco through M1 to outside world?

Check that RDR opt has CFF not CFO

Check NCOS on trunks from Ciscoto M1

Also, could be TRO or TAT issue if going in and out on same trunks.

 

[mt6322]

To clarify:

The call is not going in and out on the same tie trunks. ng
The call originates from the Merdian PBX via the QSIG PRI tie trunks to the Cisco Call Manager and then out on the PRI local/LD trunks on the Call Manager side.

The two sites have 4 digit extension Coordinated dialing plan to call each other but each site has its own PRI trunks for external calls.

When an extension on the Cisco side forwards its call to an outside number using its own PRI trunks. Calls will go through if calling within the Cisco call manager side. But if the call originates from the Meridian PBX side via the tie line, caller hears a re-order tone.

 

[Reusser]

You will need to look at the DChannel messages or work with the Carrier to determine why call is rejected.

 

[mt6322]

Upon further checking using the MSGO and MSGI messages on the D Channel I discovered that the problem is only affecting forwarded calls to the 202 area code.

Here's what is happening;

When an extension on the Cisco side is forwarded to a 9.202.xxxxxxx number and a call originates from the Meridian side via the tie line, it seems that the call is re-directed back to the Meridian side and then it picks another channel to call the forwarded number but stripping the access code 9.

I've checked and compare the parameters on the Cisco and Merdian side with other area codes but could not find any differences in the setup. I am confused with this problem, please help. Thanks.

 

[Reusser]

may want to say yes to INAC on the QSIG trunk. If call is tagged as NPA it will insert access code.