IP/XNET Trunking

[WJ2600]

Hi guys,
I have two MXe systems in 2 different locaions, I am using IP trunks to connect the systems to each other, it works fine,
due to the company cost reduction plan,we want to use one TDM trunk group only of one system A, and route all the calls (TDM) from the other system B to A through the IP trunks,

No ISDN card used,

ARS programming is made, but the calls for some reasons do not go through!
they getting stuck in system A,

Any one can help in clearing this issue or providing programming tips to solve it?

Thanks,

WJ.

 

[kwbMitel]

When you talk about ARS programming, what exactly do you mean?

Are these systems with Clustering and RDN Syncronization?

Are you faking IP Trunking with SIP trunks?

Assuming the former, what results do you get if you type the Maintenance Command on system A - Locate Extension XXXX (where XXXX = extension on system B

Expected result will be that the extension is a Remote Directory with CEID digits YYYY

I will wait for a response before going into too much more detail


**********************************************
What's most important is that you realise ... There is no spoon.

 

[WJ2600]

Thanks kwMitel,

I mean by ARS Prg. that the CO calls istead of going out through the local CO trunks, they go vial the IP trunks to the other system,

both systems are in a Cluster with RD sync.

when Locate command is used for a remote Ext. it gives me the CEID and the routing digits of the remote system,


WJ,

 

[Billz66]

we have done this before as follows
System A has no CO trunks
Sytem B has CO trunks

on system A dont strip access code but send full number ( with access code) to System B via Xnet

toll restriction is done on system A
when call arrives at system B it will use the digits sent to determine how the call is routed

If I never did anything I'd never done before , I'd never do anything.....

 

[WJ2600]

Thanks Billz66,

that is what I did exactly,

I am sending the whole digits including the leading digit to B,

But doesn't go,

WJ.

 

[kwbMitel]

IP Trunks will show up on a CCS trace

Make sure where it's failing. Statrs a ccs trace on each system and see if it is at least reaching the 2nd system or not leaving the first so that you can isolate the problem.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Billz66]

is the ars similar for both systems
- do they both use the same access codes
- is the cor of the trunk attributes for the xnet trunks able to make an external call

If I never did anything I'd never done before , I'd never do anything.....

 

[sarond]

You might also want to check "Send Travelling Class Marks" is set to yes in the System Options form to ensure COS and COR of the extension are used on the other system.

 

[jpruder]

ip trunk have public access via dpnss enabled?

 

[WJ2600]

Sorry guys that i took so long before responding to you all,

Actually, the problem is solved now,

the problem was with the phone used to test the calls,this phone is a transferred IP line; I mean by this, its registered in system A, but located in system B (remote Ext.) and getting its IP from system B,

I use this Ext. to test calls, trunks, connection between the two systems,

I was using this line to test to route the calls via the XNET,

for some reason!! the calls did not route when using this line (another issue, not important now),
Then, when asked the users of Sys.A to make calls via the xnet, they finally went through,

Thank you all for your help and support and really appreciate your advices,

Thanks again,

WJ

 

[jpruder]

FWIW, I usually setup a sip softphone on the remote end for my tests

 

[WJ2600]

Thanks jpruder,

it is also a good idea, will do it,

thanks again,

WJ.

 

[WJ2600]

One more thing guys,

just to be as a reference thread for the future,
can any one guess from the following CCS trace output, what was the reason of getting the calls stuck in system A,

Here system B report, the originator of the calls;

09:05:21 RIX DPN PBX2 226 787 D** B** 6 EEM_C *89B#
09:05:21 ROX DPN PBX2 226 787 D** B** 1E EEM_C
*55#*1#*50*4518#*58*C3*3*1*1#
09:05:22 RIX DPN PBX2 226 787 D** B** 1B EEM_C
*90#*58*CW*@Alk@@@@AHsTxP#
09:05:23 RIX DPN PBX2 252 789 D** B** 2 CRM/CIM ;30;
09:05:28 ROX DPN PBX2 224 783 D** B** 2 CRM/CIM ;30;
09:05:29 RIX DPN PBX2 224 783 D** B** 2 CRM/CIM ;30;
09:05:35 RIX DPN PBX2 242 750 D** B** 2 CRM/CIM ;30;
09:05:45 RIX DPN PBX2 237 798 D** B** 10 NSIM ;1C;*58*C3*2*40*1#
09:05:45 RIX DPN PBX2 237 798 D** B** 25 NAM
*1*1#*50*2036#*166*4#*100*6.SPARE*1#
09:05:45 ROX DPN PBX2 237 798 D** B** F NSIM ;1C;*58*C8*4470*#
09:06:01 RIX DPN PBX2 226 787 D** B** 29 EEM_I
*79*T#*4*1#*50*9772682626#*58*C3*5*62*9#
09:06:01 RIX DPN PBX2 226 787 D** B** 12 EEM_C *100*773331237*1#
09:06:02 ROX DPN PBX2 226 787 D** B** 2 CRM/CIM ;30;
09:06:02 RIX DPN PBX2 226 787 D** B** 2 CRM/CIM ;30;
09:06:03 RIX DPN PBX2 234 786 D** B** 1C ISRM_I
;10;*6#*50*2001#*58*C3*12*7*7#


And this is system A the terminator of the Calls:

09:04:57 RIX DPN PBX1 799 249 D** B** 9 CRM/CIM ;8;*166*4#
09:05:14 ROX DPN PBX1 809 254 D** B** 10 NSIM ;1C;*58*C3*2*40*1#
09:05:14 ROX DPN PBX1 809 254 D** B** 25 NAM
*1*1#*50*2036#*166*4#*100*6.SPARE*1#
09:05:16 RIX DPN PBX1 809 254 D** B** 2 CRM/CIM ;30;
09:05:18 ROX DPN PBX1 806 205 D** B** 10 NSIM ;1C;*58*C3*2*40*1#
09:05:18 ROX DPN PBX1 806 205 D** B** 25 NAM
*1*1#*50*2036#*166*4#*100*6.SPARE*1#
09:05:18 RIX DPN PBX1 806 205 D** B** F NSIM ;1C;*58*C8*4585*#
09:05:33 ROX DPN PBX1 794 263 D** B** 9 CRM/CIM ;8;*166*4#
09:05:33 RIX DPN PBX1 794 263 D** B** 9 CRM/CIM ;8;*166*4#
09:05:54 ROX DPN PBX1 811 233 D** B** 9 CRM/CIM ;8;*166*4#
09:05:54 RIX DPN PBX1 811 233 D** B** 9 CRM/CIM ;8;*166*4#
09:05:57 RIX DPN PBX1 806 205 D** B** 2 CRM/CIM ;30;
09:06:05 ROX DPN PBX1 780 228 D** B** 2 CRM/CIM ;30;
09:06:05 RIX DPN PBX1 780 228 D** B** 2 CRM/CIM ;30;
09:06:12 ROX DPN PBX1 802 253 D

WJ