DCS Over TCP/IP for Voice calls via PSTN?

Do you have IP trunks enabled in your system? If so in the trunk group form select the medium type as IP. Build the signal group (which it appersa you have allready done) and add the ip trunks. If you are trying to sends calls to the other PBX, tail end hop-off, you would have to build a route to the far end PBX, using ARS and route accordingly.

Hope this helps

Chris

Hi
Thank you Chris for the response, the Far end PBX does not have IP trunks enabled, I have not set up a signal group as the DCS link is administered in the ch communication Process.

Proc Gtwy Interface Destination Session Mach
Chan Enable Appl. To Mode Link/Chan Node Port Local/Remote ID
1: y mis s 2 5001 cms 0 1 1
2: n 0
3: n 0
4: n 0
5: n 0
6: n 0
7: n 0
8: n 0
9: n 0
10: n 0
11: n 0
12: y dcs s 2 5003 Clan_mad07 0 12 21 14

The processor channel points to link 2 this is the Clan data module the node-name is the far end clan address.

status processor-channels 12 SPE A
PROCESSOR-CHANNEL STATUS

Channel Number: 12
Session Layer Status: In Service
Socket Status: TCP connected
Link Number: 2
Link Type: ethernet
Message Buffer Number: 0

Last Failure: Far end sent disconnect messag
At: 11/16/01 11:46

As you can see the DCS link is up, but how do I Tie it to call setup over the PSTN??

Cheers Greg

DCS assumes you have point to point facilities. I also assume based on the communications channels you are showing that QSIG has not been implementated. The DCS software will pass calling information, FRL, etc between the PBX's on the D channel and coordinate the call. The calling and called PBX must be aware of the trunk status so it can connect the call together. A tandum call between switches, the CO is acting as a hub, will not pass the necessary information unless you implement QSIG to do so. The CO provider must also pass the QSIG information from switch to switch. Because there are no point to point trunks, I do not believe you can get DCS to work in this enviroment. IE You are recieving a call on trunk group 5 for station 1000, The calling PBX tells the far end PBX what trunk group the call is originating on and where to send it. Because the call is switched through the PSTN the called PBX has no idea as to which trunk group and member it will be recieving the call. If there is no point to point trunks the Definity can not coordinate the call. I'll do some looking tomorrow and check this out but I am 99% sure this is the case. I hate that nagging 1%! Hope this helps

Chris

Hi
Thank you Chris for the info and I will be interested in what you dig up, you are correct in assuming that Qsig is not turned on, we do not have any point to point E1s to run DCS across the d-channel and IP trunks is also not turned on in the far end switch.

Even though the DCS signaling over IP is up and running between both switches the problem appears to be that, this type of DCS connectivity has no way of tying to a call setup over the PSTN, what I thought and hoped would happen is:

Calling party at the near end PBX makes a call to the far end, in the near end aar ana table the dialed string is recognized as a call to far end DCS node:xx

The PBX signals to the far end PBX via the DCS IP link that a call is being made to extension xxxxx

This im not sure about but "hope" would happen: The near end PBX then marks the out going call setup using the IE's in layer 3 which is recognized by the far end PBX and Ties it to the DCS information sent over IP.

That's a BIG hope

Look forward to what you turn up Chris.

Cheers

PBX