Has anyone DPNSSed to an ISDX

[CMAC1]

I have a customer who wants to link Siemens ISDX systems to Mitel 3300's via DPNSS. Has anyone any experience? Any problems? Any loss of facilities? Any comments.........?

 

[MitelInMyBlood]

Not with a Siemens, but we looked into it once with a France Telecom machine and after discussing w/both vendors engineers it was decided E1-Q.Sig (ISO) was the way to go.

Works good, we're getting full integration transparency both ways, MWI set/clear, CFB/CFNA reason codes, name/nbr, divert, step-back on busy, etc.
Only problem I've seen is man-busying individual trunks or even the whole span on either end is not reflected across the link unless you knock down the D channel, but I think that's pretty typical with Q.Sig PRI.

We're also doing Q.Sig between a SX2K and a Cisco CM; not as robust, but name/nbr and MWI stuff works OK.
Same probs w/busyout.

Ditto Q.Sig to a Northern M1, again not as robust as with the France Telecom system, but at least name & number is getting passed both ways.

Your mileage may vary..

 

[deanmulley]

yep we have a site with a link between the 2 switches...be aware below 5.2 on the dx the multiline handsets cant produce dtmf..... (so ive been told buy one of our dx guys).
Apart from that they work great, no issues have been reported.
we use the 3300 as vm for the isdx also.( alog phones)

 

[andy4uk]

I have installed system's via DPNSS on Avaya INDeX and only one onto a siemens system. The siemens was no problem however the Avaya system's was a complete pain in the backside....!!!

 

[tilf]

I disagree, the Avaya INDeX integrates extremely well via DPNSS, most features work across the 2, its just a matter of correct setup.

 

[andy4uk]

I disagree tilf, there are a lot of functions which are lost, it all depends on the software that is running on the cpu.

On cpu-x software 10 and above there are not many problems, however all software below version 10 i would'nt bother intergrating.

As you said most features work, it's probably the features that you have'nt set up that i have had problems with.

Even a basic setup of an ISDN call via the INDeX to a Mitel handset causes a problem due to the software on the INDeX, both Mitel and Avaya have looked into this and can not find a solution apart from upgrading the Cpu to an X, not bad might as well get a new system...!!

I have lost count on how many INDeX and Mitel's I've intergrated, and on every one it's taken additional days to complete, so i would advise to allocate more days on the job that would normally take?

 

[tilf]

Just out of interest what features dont work, i have integrated loads of these in different types of scenarios and differing software levels and have always got everything to work.