I have same strange situation with call routing on Meridian 1. This switch using as a tandem node with three following routes:
1. Route 10 – to Houston, E1 PRI2, QSIG TIE trunks. Slot 1.
2. Route 11 – to Remote office in Baku, E1 PRI2, QSIG TIE trunks. Slot 2.
3. Route 12 – to oil Platform, E1 PRI2, QSIG TIE trunks. Slot 3.
Users of the Local and remote offices can do calls to Houston with no problem at all. But any direct call from Route 12 to Route 10 (and back) impossible, because Meridian 1 blocks such connection and sends message in D-channel: cause # 42 swed eqip congestion. In same time all trunks of route 10 is IDLE. Calls from the oil platform to Houston could be done only via remote office, but in that case using twice more trunks. Why? I don’t know. There no call restriction at all. All routes are have same ART=0. I have checked all settings in LD 15 and LD 86, but could not find any answer on this quest.
1. Route 10 – to Houston, E1 PRI2, QSIG TIE trunks. Slot 1.
2. Route 11 – to Remote office in Baku, E1 PRI2, QSIG TIE trunks. Slot 2.
3. Route 12 – to oil Platform, E1 PRI2, QSIG TIE trunks. Slot 3.
Users of the Local and remote offices can do calls to Houston with no problem at all. But any direct call from Route 12 to Route 10 (and back) impossible, because Meridian 1 blocks such connection and sends message in D-channel: cause # 42 swed eqip congestion. In same time all trunks of route 10 is IDLE. Calls from the oil platform to Houston could be done only via remote office, but in that case using twice more trunks. Why? I don’t know. There no call restriction at all. All routes are have same ART=0. I have checked all settings in LD 15 and LD 86, but could not find any answer on this quest.
