using PCM trunks for DID/DOD via ISDN link

[Xero]

Hi,

We have an OXE Release 6.2, it is integrated with Cisco on a T2 trunkgroup connected to NPRAE. There is a PCM provided by telco for DID/DOD configured in OXE and it is used by all OXE extensions. Now we want to use the same DID/DOD for cisco extensions. We have created a testing extension in Cisco using the same range as of OXE and are successful in DID calls but for DOD we are getting "NO ROUTE TO DESTINATION" message in t3 traces of NPRAE T2 trunkgroup.

For testing purposes we have tried outgoing calls from Cisco using Analog trunkgroups in OXE and were successful but we are unable to do DOD calls.

[cavagnaro]

It must be done in the OXE not in Cisco. On the DID translator instead of subscribing an OXE extension just put the normal Cisco extension you are used to dial.

[Xero]

Hi Cavangaro,

We have already configured DID translator in OXE that's why we are recieving incoming calls on Cisco extension, but the problem is with DOD calls using this cisco extension. Can you please elaborate further more what you have proposed?

[haroun]

and what's the cisco's extension config at oxe side? abreviated numbers, networks numbers , routing ones
T2 trunkgp between oxe and cisco is public or private , check trunkgp PNC May cos is blocking external calls

[haroun]

also post t3 traces when ongoing call

[Xero]

Dear Haroun,

Extension in Cisco is 19605, also we have similar range in Alcatel like 19601,19602.... but not 19605. In alcatel we have configured 19 as a routing number towards the T2 TG between OXE and Cisco this is " Private Trunk Group + False". Below are the t3 traces when we are making outgoing call using 19605. here 447 is the DOD TG seize prefix and 0550057602 is the dialled number



______________________________________________________________________________
| (440896:648514) Physical-Event :
| long: 53 desti: 0 source: 0 cryst: 2 cpl: 13 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 67 ff
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 98 -> T2 : B channel 24 exclusive
| IE:[6c] CALLING_NUMBER (l=7) -> 09 81 Num : 19605
| IE:[70] CALLED_NUMBER (l=14) -> 80 Num : 4470550057602
|______________________________________________________________________________

______________________________________________________________________________
| (440896:648515) 1092: Send_IO1 (link-nbr=22, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 2 cpl: 13 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP ACK [0d] Call ref : e7 ff
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a1 83 98 -> T2 : B channel 24 preferred
|______________________________________________________________________________

______________________________________________________________________________
| (440896:648516) 1092: Send_IO1 (link-nbr=22, sapi=0, tei=0) :
| long: 18 desti: 0 source: 15 cryst: 2 cpl: 13 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : e7 ff
|______________________________________________________________________________

______________________________________________________________________________
| (440921:648517) 1088: Send_IO1 (link-nbr=22, sapi=0, tei=0) :
| long: 35 desti: 0 source: 15 cryst: 2 cpl: 13 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CONNECT (07) Call ref : e7 ee
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 80 82
| IE:[4c] CONNECTED_NUMBER (l=7) -> 00 81 Num : 71364
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> EXTENSION (1)
|______________________________________________________________________________

______________________________________________________________________________
| (440921:648518) Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 2 cpl: 13 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CONNECT ACK (0f) Call ref : 67 ee
|______________________________________________________________________________

______________________________________________________________________________
| (440937:648519) 1088: Send_IO1 (link-nbr=22, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 2 cpl: 13 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : e7 ff
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 80 83 80 -> [83] NO ROUTE TO DESTINATION
|______________________________________________________________________________

______________________________________________________________________________
| (440937:648520) Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 2 cpl: 13 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 67 ff
|______________________________________________________________________________

______________________________________________________________________________
| (440938:648521) 1088: Send_IO1 (link-nbr=22, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 2 cpl: 13 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : e7 ff
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 80 90 80 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

[haroun]

and you see the call at pcm trunk (or in pcm r2 traces)?
mean oxe do not undersand where to route this call -447-
other thing is it trunk cos for each type of trunk (t2 and pcm)=5 check connection cos for cos=5 with cos =5 it's should be =1 (authorised)? transit authorised?!
also give the t2trunkg public cos

[haroun]

you said that you have did but no did trancoding is done,did is same extension number calling number
Als you have 1960119602 as EXTENSIONS number aNd in OXE translator 19 as routing number? OXE SHOULDNOT ACCEPT THIS

[Xero]

Dear Haroun,

I dont see the call on PCM trunk.

Trunk cos for PCM is 26 and T2 is 19 and both have connection category 5, and cos 5 is authorized. so transit is authorized.

DID transcoding is enabled on PCM trunk group not on this T2 but the DID is working fine, as cisco extension is 19605 and DID is 07 23 19605

Yes my numbers in Alcatel are 19601, 19602.... and in cisco I have made 1 testing extension as 19605, you are right that we cannot use 19 as a translator if these numbers are already used, but routing number case is different you can create routing numbers even if you have same range of numbers used in translator. you can try it in your system it works.

[vad]

If you receive from Cisco - 4470550057602 - I hope in OXE - NPD for T2 TG - DID transcoding not used (Called DID Id=-1).