Dear Vad,
Yes in OXE I am reciving 4470550057602 from cisco where 447 is the PCM TG seizing prefix and the NPD of both T2 and And PCM is 3 and the DID transcoding Called DID as well as Calling DID are "0" as "0" is the DID translator I am using
using PCM trunks for DID/DOD via ISDN link
Re: using PCM trunks for DID/DOD via ISDN link
Use for test in T2 TG - NPD without DID transcoding (called DID=-1).
-
Xero
Re: using PCM trunks for DID/DOD via ISDN link
Called DID will be for incoming call, and I have no problem with incoming call. Should I do the test for called DID or Calling DID (outgoing)?
Re: using PCM trunks for DID/DOD via ISDN link
Called DID - for incoming calls. You receive from T2 (Cisco) - 4470550057602 - and want to establish transit connection. I think you cannot manage DID rules for such connections.
When you receive digits from Cisco - I think you need to use T2 TG without DID transcoding.
When you receive digits from Cisco - I think you need to use T2 TG without DID transcoding.
Re: using PCM trunks for DID/DOD via ISDN link
use pcm and mfR2 traces
performe those traces and see who is calling if the cisco extension it should be transcoded as pcm did config .
second test put trancoding under t2 trunk (between oxe and cisco ) to -1 no did/dod transcoding and redo the test .
tuner km
tuner ctr
actdg all=off
trc i
tuner appli-trace=on
actdbg mf=on
mtracer -a
performe those traces and see who is calling if the cisco extension it should be transcoded as pcm did config .
second test put trancoding under t2 trunk (between oxe and cisco ) to -1 no did/dod transcoding and redo the test .
tuner km
tuner ctr
actdg all=off
trc i
tuner appli-trace=on
actdbg mf=on
mtracer -a

