Octel 250 (Aria) to Nortel Meridan (DMID)

[omac112211]

Octel 250 connecting to a Nortel Meridan integrated using a DMID.

Every now and again users are unable to connect to voicemail and hear engage/busy. Ports on the voicemail aren't in use and a waiting idley while on the Meridian several channels are showing up as either busy or locked.

Port testing on the Octel returns Dial-tone and Loopback pass.

Any ideas?

 

[KenMeans]

has the Octel been upgraded in the last year or 2 and if so what software are you running on? there were some problems with one that you needed a patch to fix some dmid problems.

Ken Means

http://www.tel-is.com

 

[KenMeans]

This could also be the ports on the Nortel not disconecting after a caller has hung up it is a setting in the COS i will look it up.

Ken Means

http://www.tel-is.com

 

[joeOctel]

You could also check the Status Log to see if there are errors to indicate a problem. You could also call each of the voicemail ports to make sure that all of them answer correctly.

 

[KenMeans]

this may help

5.1 PROGRAMMING THE SINGLE-LINE PORTS
Programming the single line ports
These ports are used for the voice path.
o Using overlay 10, program a unique directory number (DN) for each Analog TIC port. Program the ports as follows:
REQ NEW
TYPE 500 Single line interface data block
TN lll S CC U Terminal number: loop
CUST 0-31 or 0-99 Customer number
DN XXXX Directory number (see note)
HUNT XXXX Hunt to next key appearance
CLS XFA Transfer allowed
DTN Digit tone
HTA Hunting allowed
LDTA Line disconnect tone allowed
(Release 17 and above)







8.7 Meridian M-1 PBXs require Release 17 or greater to support a positive disconnect for 2500-single line sets - with the exception of Option 11 PBXs in Canada which require Release 18. Octel strongly recommends that the PBX be at a Release that supports disconnect signaling. If disconnect signaling is not supported, the Octel 350 must rely on silence detection to disconnect. If callers and subscribers do not exit the Octel 350 properly, ports might take longer to disconnect causing extra port traffic. It is recommended that subscribers be trained to exit the Octel 350 completely when finished (by “starring” out) and that limited or extended caller prompting is set (via class of service) to prompt outside callers to also exit properly.

Ken Means

http://www.tel-is.com