Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DASS link problem - CS1kE to Mitel Switch

Status
Not open for further replies.

riscyrich

Technical User
Sep 7, 2005
60
GB
Hi All,

Wonder if you guys can help out with an issue we're experiencing...

Long story short is we've moved HQ recently and are trying to re-establish a link between our switch and a partners. Used to be DPNSS but they requested a change to DASS due to an issue their end. We've got the circuit up and I can call extensions on their switch but they can't call us. Logs seem to suggest that they are not passing enough information for the CS1KE to acknowledge the extension required. Logs below, any ideas? The CRM/CIM 1A code doesn't help as I can't find it in CCS Trace documents.

Thanks in advance.

Rich


Call Connects:
CS1kE ----> Mitel
x4182 DASS2 x2706

CS1KE Log:
DAO R 51 31 1 ISRM-I 10 2706
DAI R 51 31 1 NAM *86*2706#
DAI R 51 31 5 CCM
DAO R 51 31 4 CRM 30
DAI R 51 31 4 CIM 30

Mitel Log:
15:13:32 RI8830 DAS 6 ISRM_I/ ;10;2706
15:13:32 RO8830 DAS A CAM/NAM *86*2706#
15:13:32 RI8830 DAS 1 CA
15:13:34 RO8830 DAS 1 CCM
15:14:59 RI8830 DAS 2 CRM/CIM ;30;

Call Fails:
Mitel ----> CS1kE
x2706 DASS2 x4182

CS1KE Log:
DAI R 51 1 0 ICI-C 10 *86*2706#4182
DAO R 51 1 6 CRM 1A
DAI R 51 1 6 CIM 1A

Mitel Log:
15:15:47 RO8801 DAS F ISRM_C/ ;10;*86*2706#4182
15:15:47 RI8801 DAS 2 CRM/CIM ;1A;

Circuit coming up info:

>ld 75

DTM000
.enl ddcs 51

OK
.enl ddsl 51

OK
.strt 51

OK, STARTING
.
DTM301 51

DAI R 51 1 0 CIM 1A
DAO R 51 1 6 CRM 1A
DAI R 51 2 0 CIM 1A
DAO R 51 2 6 CRM 1A
DAI R 51 3 0 CIM 02
DAO R 51 3 6 CRM 1A
DAI R 51 26 0 CIM 1A
DAO R 51 26 6 CRM 1A
DAI R 51 27 0 CIM 1A
DAO R 51 27 6 CRM 1A
DAI R 51 28 0 CIM 1A
DAO R 51 28 6 CRM 1A
DAI R 51 29 0 CIM 1A
DAO R 51 29 6 CRM 1A
DAI R 51 30 0 CIM 1A
DAO R 51 30 6 CRM 1A
DAI R 51 31 0 CIM 1A
DAO R 51 31 6 CRM 1A
DAI R 51 1 6 CIM 1A
DAI R 51 2 6 CIM 1A
DAI R 51 3 6 CIM 1A
DAI R 51 26 6 CIM 1A
DAI R 51 27 6 CIM 1A
DAI R 51 28 6 CIM 1A
DAI R 51 29 6 CIM 1A
DAI R 51 30 6 CIM 1A
DAI R 51 31 6 CIM 1A

DTM000
.stat ddcs

DDCS 051 ENBL
.stat ddsl

DDSL 051 ENBL ACTIVE
 
Hello Rich

It might be best to continue this query off line. I've been dealing with issues along the same line for a customer who has a Meridian Option 11c at V25.40 with DASS ISDN 30 trunks. They also had a Mitel 3300 fitted last year that was attached to the Meridian via a DPNSS 30 Channel link so that any calls from the Mitel 3300 went via the DPNSS into the Meridian and out through the DASS to make the voice connection.

The first thing I would say is that you should have stuck with DPNSS. DASS is only to be used from the switch to the exchange. DPNSS was designed to be used as a inter PABX link.

The problems that I came across were really the Mitel,s problem.

SPN's. In the UK, we have "0" as the start of our national numbers and not "1" as is used in other countries. We found that calls that failed were mainly SPN's 01,02,08 etc.
What we had to do was to expand the SPN's such as..010 to 019, 020 to 029 and perhaps 080 to 089.

SPN 010
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 011
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 012
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 013
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 014
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 015
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 016
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 017
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 018
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

SPN 019
FLEN 11
ITOH NO
RLI 1
SDRR NONE
ITEI NONE


The other problem that we have and it's still an issue in some cases is when the customer dials a 10 digit code. Most of the UK numbers are 11 digits, but we still have some exchanges where it remains at 10!. We get reports from time to time that Mitel extension users can't call them, yet we can make the call OK from any Nortel phone.
I did as you did some DPNSS monitoring in LD 75 and went through each digit dialled from Mitel extension making a 10 digit call. We spotted that the Mitel system didn't pass on the "end of dialling" command to the Meridian.
In our case, the Mitel system was looked after by a different company and we weren't able to get the support we needed.
What we did in the end was to simply tell the customer to add an extra digit at the end. Problem solved!


All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
Have you tried using the INST in the RDB to add some digits then LSC to strip them back off, just we used to have something like that on a previuos site and was never quite sure why it was there.
 
Thanks for the replies guys.

I for one wasn't keen on using DASS, as already mentioned it's for exchange links but their maintainer asked that we try as apparently it's common for the Mitel engineers use DASS between their switches???

Anyway we've had another session of tinkering with various parms either end but have decided to head back down the DPNSS route and try solve the problems we had - the Mitel switch instead of following forwards on our extensions but calling the extension on their switch i.e.

x2706(Mitel) calls x4182(CS1kE)

x4182(CS1kE) is forwarded to x4333(CS1kE)

CS1kE tells Mitel x4182(CS1kE) is forwarded to x4333(CS1kE)

Mitel switch connects x2706 to x4333(on the Mitel ? ? ?)

Bit bizarre but perhaps a discussion for another thread...

Many thanks,

Rich
 
I'm assuming that your Mitel switch is a 3300?. It's a long winded process that you have!. Another thing I should have stated is that with DPNSS, you should have each end setup as either the A or B end!.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
Our switch is a CS1kE running R7.5, their switch is Mitel 3300 MCD6.0

The good old DPNSS link between us has worked for years, till they upgraded. Calls from us to them are fine, it's the Mitel that gets it wrong coming the other way when the extension they call on our CS1kE is forwarded. It sees that our extension is forwarded to xxyy and then says oh I have an xxyy too, I'll forward to my one.

[ponder]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top