Interesting problem with forwarding DID calls to TIE trunks 1

[T1PSTN]

I have 2 PBXs in my company. A user moved from one PBX (DID range) to the other PBX (with a different DID range.) I made his DN a DSC in the PBX that he moved from, and built a phone with his DN on the PBX that he moved to. Everything works great... until users from a few other locations try to call the user via his original DID. All DID calls come in over the same PRI span. Sites that have Meridian PBXs go right through, and sites with Avaya PBXs go to the attendant. POTS lines from my building go to the attendant, but the payphone in my lobby goes to the intended user. The DCH messaging does not indicate that the call is being directed to the other PBX (on which the users phone is equipped) when the calls go to the attendant. For successful calls, the DCH messaging shows the connect, ack, alter, and so forth for both the DID and the TIE that the call has been routed to. Can anyone offer me any advice please?

 

[Reusser]

In CDB NET_DATA - try setting DITI to yes. If that doesn't do it, try FTOP to FTTB or FTLY

Also, is there a difference in DCHN message (call type) for calls that do and do not work?

 

[T1PSTN]

Reusser- Thanks for the input. I had tried DITI, still no go. I found a way around the problem by unplugging the DID span from the Meridian, and plugging it into the other PBX. The other is a Cisco CallManager, which doesn't seem to have any problem with the originator's numbering plan. That seemed like the real sticking-point since all originators except E164 types worked fine.
What a wierd problem... maybe an X11 software glitch?