3300/2K XNET over ISDN issue

[kwbMitel]

I am trying to locate an issue where I am getting XNET busy when calling site to site. Both sites have sufficient channels of ISDN and the XNET TDM trunks are maximized as well.

Bottom line, lines are available but XNET busy is displayed.

It occurs to me that the issue may be that I have too many trunks. Site A is a 2K with 4 Spans of PRI. 2 are are a PRI card in a DSU bay and 2 are on an NSU.

When checking the status of the HDSL links I noticed that the link is established on the DSU PRI. The status of the HDSL links on the NSU are indeterminate - meaning they have never been used since the last reset.

It occurs to me that I might have an issue if the Voice Channel trys to establish via the NSU while the Data Channel is on the DSU.

Does this seem reasonable?

Assuming all programming is correct (99% certain) and channels are available (100% certain) can anyone suggest a scenario where XNET busy will be returned intermittantly?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

3300 is rel 7.1
2K is LW 34.1.0.6 (redundant)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Another question on the same subject.

Can a 2k Utilise XNET over IP directly to a 3300 or would it need a 3300 gateway connected via MSDN?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mitelmmaniac]

Hi KwbMitel

You would need a gateway for the ip trunking.

where are you? US/Europe?



Desk Jockey Lunacy

 

[kwbMitel]

Mitelmmaniac - I am in Canada

That is what I expected but I started to doubt myself.

Thanks.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mitelmmaniac]

Cool, well I am in the UK so I am not sure how it works in North America, never really take much notice when reading docs.

Is it an isdn link (in the uk its DPNSS)
Here you can only use either qsig or DPNSS to connect a TDM and IP pbx.

Desk Jockey Lunacy

 

[LoopyLou]

How many DID's are you using for your XNet. From what I recall (and its been a while ) you need a DID for the data part ( D shannel of your fake MSDN link )and a seperate DID for the voice ( B channel of your fake MSDN link ). In case of lots of traffic you need multiple DIDs becuase there is a short time during call setup that the DID will actually be busy ( don't ask me why )and that's why the multiple DID's are sometimes needed. Also there is a timer on how long that Data DID stays up waiting for other calls before it drops, again lots of call leave that data DID longer so you are not having to redial that data DID number. Not sure if this helps or not.

 

[mitelmmaniac]

I think its a bit different where you are so I will butt out.

Desk Jockey Lunacy

 

[mitelmitel]

How many Xnet trunks have you programmed for the link? Have you set up a traffic report?

I suspect programming/and or resources.

 

[kwbMitel]

All programming and resources have been verified to within 99% of certainty as stated earlier.

Has anyone ever setup XNET over PRI where there are more than 2 PRI's available and thus the 'D' channel and 'B' channels might be setup on separate NSU's?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[LoopyLou]

No have never implemented across multiple PRI spans and that might be the issue. Ever tested at low traffic with both B and D going out the same channel?

 

[kwbMitel]

Yes, i've tested but incedence is too low to duplicate.

I've forced the issue for now to see what happens.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[LoopyLou]

Sorry, I said test with both out the same PRI, I should have said test with B out one and D out another PRI but judging by the quality of your posts you know what you are doing. I did ask before how many DID numbers you had assigned to the implemenation but you never really said with the exception that the setup is programmed correctly and enough channels were assigned.

 

[kwbMitel]

I finally had enough of this one and called Mitel. There are several Dpars with respect to Xnet Busy that are fixed is software levels above what is active on site.

They tell me the signalling channels and B channels do not need to reside on the same PRI card or NSU.

the solution to my problem appears to be upgrading.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.