CDP interconecting PBX

[AlbertDT]

Hi! My friends.

I have a situation a 3 PBX (an OPc81, OPc61 and OPc11) interconected by way of T1. The thing is that we use CDP Type DSC to acces DN's on the other PBX and works fine from one PBX directly terminating in another, but when we try to dial a DN from PBX (A) that it's CDP Type DSC to PBX (B) but in PBX (B) this DN it's CDP type DSC to PBX (C) the call can't terminate on PBX (C) and give busy signal.

The thing is that the client it's constnatly making changes and crazy moves and I want to know if there is a way to acomplish this just for keep running until the client decides to move the DID's block from the PBX PRI's so I can do the changes on the CDP RLI's.

Thanks!

 

[pronei]

Sounds like you will need to use Location codes in your dialing plan if you have conflicting DID ranges.

 

[GHTROUT]

I'd be looking at the Route Data Block NEDC and FEDC settings, as well as the CLS and NCOS of the TIE trunks in each PBX.

Also if ESN is set to YES in the RDB, then you end up with "traveling NCOS", meaning the NCOS of the caller is delivered between sites - I doubt that is the problem, but it's worth looking at if the first efforts fail.

GHTROUT.com | FAQs | Recent Replies

 

[trvlr1]

Do you have the connections from one of the PBX to the other two, ie 81 to 61 and 81 to 11? If so the problem might be that when you dial one of these numbers the CDP is sending from A to B, but B is sending it back to A. Eventually the T-1 between the two sites will use up all it's channels and you get a busy signal. The only way to get around this is to make sure the users follow the correct procedures for CDP's in all 3 PBX so when they move a number between the sites they also change the corresponding CDP settings, or get you to. Otherwise they are going to have a lot more issues. Also, have you thought about 911 calls when moving numbers between sites, making sure your set up allows emergancy services to know where it is coming from accurately?

 

[AlbertDT]

Yes You are right and we are always trying to implement this but the client don't cooperate to make an uniform Dialing plan, so in the meanwile this is my situation. They are closing offices on an building and moving from one PBX to another and then they want to move a PRI circuit to another PBX or a DID Block to another PBX but some of the DN's that are DID's still on the other PBX, the CDP thing needs to be rearenged.

But for resolving temporary this CDP thing, I don't know if there is a parameter on the routs that help to acomplish by CDP DSC hooping from from one PBX to another to another.

 

[trvlr1]

I don't know of any other way of doing this that would be less work than changing the CDP's. Maybe when they move one of the "bigwigs" and their phone does not work, they will get the picture .... we live in hope!

 

[AlbertDT]

GHTROUT, I will check this parameters, TRVLR1 yes we have T1 connection from A to B, from B to C and from A to C so when you dial from one PBX to another it works fine the CDP thing but but if you want to go by CDP from A to C passing from B so the call hangs up.

Example: DN 7082 is on PBX (C) so it's CDP DSC to C on A and B, this works fine but when we try to dial 7082 from B that is CDP to A and in A 7082 is CDP to C that it's the final destination it can't work.

Thanks!

P.S. excuse for the slow response, maybe you already ansuerme something that I am trying to ask when I'm typing.

 

[tnphoneman]

Calling from site a to site c but you have to tandem through site B to get there. Trunks incoming from site A must have a NCOS high enough to allow the call using CDP to site C. If the Ncos is 0 but the RLI says you must have FRL 1 then the call will be blocked.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.