PPP DCS - Oldie, but not so goodie

[cycledick]

I've got a 7 site system that has 7 seperate systems (and centralized voicemail) that are all DCS'd together via the "old" PPP method of DCS (No ISDN). It is not a hub-spoke design because the customer wanted redundancy with their point-to-points. So, there are various point-to-points going between various sites to allow calls to take a different path if the primary point-to-point is down. The "data" channel that provides all the DCS info (mwi and the like) is in a seperate trunk group than the "voice" channels. DCS integration is established by a data module on one side calling a data module on the other side and establishing a ppp connection. In every instance I've seen of this configuration, the way to do this is to have the data module dial the TAC of the "data" trunk group, then the far-end data module's extension. Because the data modules are dialing the TAC, how on earth could I have a redundant DCS link? I can see how I can have redundant 4-digit dial, but not the DCS link since it's dependant on the TAC.

Anyone know if it's even possible to do that?

 

[lopes1211]

You are just talking about the individual links. It's the multiple links combined with route patterns which give you the redundency (keep in mind I dont really agree with the design you have described as more trouble than it's worth)

If site A is connected by DCS links to sites B & C.

Then sites B & C each have a connection to site D.

The route pattern for site A to call site D would typically have 2 entries, 1 to send the call over B's DCS trunk group and 1 to send calls over C's DCS trunk group. If B's link went down, the call would go out through the link to C because of the route pattern. It's no matter that the "A to B" data link is setup using a TAC no more than the "A to C" data link is setup using a TAC.

-CL