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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RS232 Questions VM Transfer

Status
Not open for further replies.

dschartung

Technical User
May 11, 2004
79
US
Can anyone here explain to me how the NEAX 2000 series transfers calls to external voicemail using RS232/Serial?

I want to replace our Mitel VM server with an Asterisk solution, but two things are stopping me; call transfer to voice mail and voicemail transfer to the switch. Our IVR will notwork without this either. So the NEAX uses in-band signaling and RS232 to transfer where the call is originating from and which mailbox to route to. But is there documented protocol for this?


-thank for any help

Derek
 
You have the option either or but not both. You can either choose serial signaling or inband signaling. You cannot chose both on the same system.

Serial signaling uses the MCI with the national SMDI protocol developed by Bell. It has more information and reason codes for the call. i.e. calling party, called party, and trunk route information.

Inband signaling or dtmf signaling will only give you the called party information and only one reason code i.e. forwarding.

Post again what you are looking for in more detail.

 
IVS2 and IPS allow for both Inband and MCI(RS232) using command 1324.

Mextera

Mextera
 
Yep we're using MCI. Is there a spec or code for SMDI?
 
Here is what I found on teh Internets:

Call History Information Message
• Type 1
– crlfMDgggmmmmaxxxxxxxxxx_yyyyyyyyyy_crlf[Control Y]
– Message includes calling as well as forwarding station
identification, valid except when a=D
• Type 2
– crlfMDgggmmmmaxxxxxxxxxx__crlf[Control Y]
– calling station identification omitted
• Type 3
– crlfMDgggmmmma_ yyyyyyyyyy_crlf[Control Y]
– direct call, not forwarded a=D

An asynchronous serial data transmission protocol is used on the SMDI link.
Each word of the message consists of a start bit, a 7-bit standard ASCII
character, an even parity bit, and a stop bit.
Call history information messages are messages to the Message Desk.
Crlf - carriage return followed by line feed
ggg - message desk number (001 - 999)
mmmm - message desk terminal (0001 - 9999)
xxxxxxxxxx - forwarding from station number
yyyyyyyyyy - calling station number
a - D Directly dialed call to the message desk
A All calls forwarded to the message desk
B call forwarding from a busy line
N Call forwarding upon no answer
U Call has been forwarded, reason unknown.
_ ASCII space character
[Control Y] - end of the message
 
See OzzieGeorge postings for manuals. He indicates that you can find the manuals on:


In the feature programming manual you will find the complete specs for the MCI/SMDI.

No, you cannot do both serial and inband on the same switch due to command 08>443 which selects either serial or inband for the entire switch.



 
Our other option is the Panasonic Voicemail which uses in-band. Is the Panasonic recommended?

Thanks
 
Not to conflict with CTVI, But with 08>443 set to a 0 and 1324 for the inband ports this allows for both MCI and Inband in the same PBX.

Mextera
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top