call forward on linked PABXs 1

[Roo Richards]

in the middle of a migration in Australia, moving a network of 6 PABXs from ICS120 to IPS. the only one left as a 120, is the main site (switch A)

make a coffee, settle down, this isnt going to be a quick one I suspect. see the diagram below to get your bearings


main PABX is ICS7400/120 (call this switch A)
this has
[li]ISDN public indial trunk [/li]
[li]QSIG link to Asterix box [/li]
[li]#7 link to IPS transit PABX (switch B)[/li]
[li]closed numbering eg no access codes[/li]

ISDN trunk is Rt10
QSIG trunk is rt03 to Asterix PBX (call centre and voicemail)
#7 link is rt30 to IPS PABX as a transit switch (Switch B)

IPS PABX switch B is primarily a transit switch to be able to connect the old ICS120 (switch A) to 4 other IPS PABX down the track using IP trunks, lets call these other switches collectively switch C (doesn't matter which one we use as its IP trunks in a network)

switch B has
#7 trunk to Switch A
#7 IP trunks on rt25


An indial call from the PSTN to distant extension on switch C, comes in on ISDN indial trunk on switch A, routed via rt30 to IPS (switch B) then out through IPT rt 25 to switch C (all good works well)


on switch A, I call forward an extension phone to the voice mail - usually on no answer - we would forward extn 720 to 9,720 (720 being the extension number) 9 routes the call to rt 03 into the voicemail in the asterix. all good.

then we needed to provide some IP extns to a remote office and the quickest way was to attach them to the IPS switch B.

so PSTN call in via ISDN to switch A, out through #7 rt 30 to the IPS Switch B, then to IP extension all good
(mucho manipulation of the routing tables to pull out individual extns but it works!)

now I want to get voicemail working on an IP extn 789, which connected to switch B. so i forward no answer to 9.789

8A4003 de 9 de 0030 (saying route a call with 9 through rt 30 back to the switch A)

if I dial 9789 from extn 789 on switch B, i get through to the asterix voicemail, proving that i can dial from switch B to switch A and out to the asterix

if I call from either switch B extn OR a switch C extn to extn 789 , it works, the inbound call forwards from switch B, across the #7 to switch A out through rt 03 to the asterix. all good as the call is in one direction from C through B to A

my problem is, if I initiate the call either from the PSTN, via ISDN on switch A, or from an extn on Switch A, to an extension in Switch B, the call will not forward no answer, BACK through rt30 to switch A and then out rt 03 to the asterix (yes cmd36 is sorted)

I suspect something to do with trombone trunking collapse??


ICS120 (A) IPS (B)
------------ ------------
| |rt30 rt30| |rt25
ISDN------|rt 10 |-------------| |-----------> to Switch C's
| | | |
| | | |
| |rt03 --------------
| |-----|
------------- | --------------
| | |
| | |
--------| |
| |
--------------
ASTERIX

the eventual plan is to replace the Switch A with a 9300 or similar but that is a few months off, so i need a fix in the meantime


thanks for any assistance

Roo

 

[OzzieGeorge]

Ok so I am too rusty to answer this without considerable effort and I suspect Belvedere will be more qualified to help but just to help out, what we Ozzies call the ICS 120 is known in the US as the IVS, we have the same name for the IVS2 and IPS though! Hope this helps!

 

[belevedere]

It's a bit much going around in circles.
My first thought is that CMD 360 is missing a route to route connection as allowed. In 360 I usually allow all combinations including my own route. EX: 360>0303:0, 1030, 3010, 3030, etc.
My next thought was that your CF maximum has been met. The old IVS allowed only 96 forwards off premise. Each forward counts, so a CF busy is one, CF no ans is 2, etc.

 

[Roo Richards]

Belvedere you are correct it is a bit of circular activity but hopefully not for long.

You were right on the money, it was a 360>3030 limitation, opened it up and it all worked

Thank you