SMDI on Octel 250

[HmmG3]

I'm trying to setup a SMDI link between an Octel 250 and Cisco VG248. I had some leftover connectors that we used to connect some VG248s to Octel 350s, but it doesn't appear to work. Are the 9 pin Async ports on the 250 different the 25 pin ports on the 350? I used a standard 9 to 25 pin serial adaptor to make the VG248 adaptor fit. The VG248 says there is a link, but the Octel says the link is down.

Any feedback is appricated. Thanks.

 

[KenMeans]

I have used a 25 pin to 9 pin modem cable on the 250 and a Cisco before and it worked fine. You mat need a null modem in the line. Have you run the TDC on the Octel side to see the raw data coming into the async port ?

Ken Means

http://www.tel-is.com

 

[HmmG3]

I didn't know about that TDC command, very nice. Looks like I'm not getting any data from the VG248. Also the Octel isn't sending any data, but that's not surprising considering it thinks the link is down.

When I first set it up, I tried all the various combinations of a null modem and straight/rolled RJ45 cables. The VG248 says there's a link with straight through cables. Oddly enough the VG248s on our Octel 350s say there is no link, but work. It's looking like I may have to bring in our support vendor to make sure we get the right cabling to start receiving the data.

 

[KenMeans]

The link on the Octel will not come up until it see's a vaild SMDI packet. I will see if i can find some more info out for you as we have many systems like this.

Ken Means

http://www.tel-is.com

 

[KenMeans]

. This COM port will connect to the Octel 250 Async port via the Lucent/OMD-provided RS-232 cable (P/N 057-1323-000) and a customer-provided DB25-to-DB9 connector.

Ken Means

http://www.tel-is.com

 

[KenMeans]

Octel 250
Message Server
Configuration Note 5405 - Ver. D (2/01)
Cisco CallManager 3.0

1.0 METHOD OF INTEGRATION
With RS-232 integration, call information is transmitted over a digital link between the PBX and the Octel 250
With RS-232 integration, call information is transmitted over a digital link between the Cisco CallManager and the Octel 250?. Voice communications are provided by a separate path created by a hunt group of analog stations on the Cisco CallManager that connect to FLTs within the Octel system. When an incoming call is received by the hunt group, it is accompanied by a digital message in standard SMDI format from the Cisco CallManager, which contains call information. The Octel 250 then answers the call on the specified port and plays the appropriate greeting. To set or cancel message-waiting notification, the Octel 250 sends a digital message over the RS-232 link to the Cisco CallManager.
2.0 OCTEL 250 ORDERING INFORMATION
Octel 250 requirements
• Fax Line TICs (FLTs), 8 ports per board
• Disk drives
• RS-232 integration software
NOTE: Serial channels 1, 2, and 3 in the Octel 250 are configurable as either RS232 integration links or system management terminals (SMTs). When used to support an SMT these channels require a null modem. Channel 4 is reserved for SMT use and does not require a null modem.
The following table shows the allowable combinations of integration links and SMTs:

3.0 PBX HARDWARE REQUIREMENTS
PBX hardware requirements
• Cisco CallManager PC with one available serial (COM) port
• Analog station ports, one per Octel port. Analog Station ports are provided via FXS ports on Cisco Analog Gateways, such as AS-4, AS-8, VG200 Gateways or WS-X6624-FXS Analog Interface Modules
• One analog station port for remote service access
• Cables, 25-pair, male-amphenol, one per FLT
• DB25-to-DB9 connector
3.1 PBX SOFTWARE REQUIREMENTS
PBX software requirements
• Minimum Software: Version 3.0
4.0 SUPPORTED FEATURES
Supported features
• Station forward to personal greeting
- all calls
- busy
- ring-no-answer
• Message-waiting notification
- lights only
• Outcalling
• Automated attendant - See Section 8.1
• Multiple return-to-operator
• Direct call
• Reply to message left by subscriber in internal telephone-answering mode
• Call Sender - See Section 8.1
Configuring the Cisco CallManager for integration

5.0 CONFIGURING THE CISCO CALLMANAGER FOR INTEGRATION
The Cisco CallManager allows integration to Octel 250 systems through the Cisco Messaging Interface (CMI). This interface provides an SMDI data stream to the Octel 250. Voice connectivity is achieved over analog lines from Cisco Analog Gateway ports. The following steps are needed to properly configure the Cisco CallManager software to integrate with the Octel 250:
? The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded. To verify that CMI is installed, open CallManager Administration. Select Service. Cisco Messaging Interface should be one of the available services listed.
? Add the Analog ports in CallManager Administration. Open CallManager Administration.
Select Device. Select Add a New Device. Click Next.
Select Device Type. Select Gateway. The Gateway - New screen is displayed. Click Next.
In the Device Type box, select AS-4 Gateway if using AS-4 Gateway(s); select AS-8 Gateway if using AS-8 Gateway(s); select Cisco Catalyst 6000 24 port FXS Gateway if using WS-X6624-FXS Analog Module ports; select Cisco VG200 if using Cisco Voice Gateway 200 ports. For additional information on Cisco VG200 configuration, refer to section 5.1.
Click Next. When adding Analog Access gateways (AS-4, AS-8, Cisco Catalyst 6000 24 Port FXS Gateway), the Device Wizard - MAC Address screen is displayed.
In the MAC Address box, type the gateway's MAC address. The MAC address is the 12-character number on the rear (AS-4, AS-8) or front (Cisco Catalyst 6000 24 Port FXS Gateway) of the gateway. For example, 0010EB001C11. In the Description box, type a description, such as Gateway1 or Voicemail. This is an optional box.
In the Device Pool box, select the device pool you want this gateway assigned to. The device pool determines the Region, Date/Time Group, and CallManager Group the gateway will use.
In the Load Information box, select Default.
In the Country Code box, select the country in which the gateway is located from the drop-down selection box.
Select a valid Location and Calling Search Space, if required, or leave those two fields to <None>.
In the Port Selection Order box, select the order you want the ports to be selected on the gateway. Top Down means the channels are selected in descending order from 1 to 4/8/24; Bottom Up means the channels are selected in ascending order 4/8/24 to 1. If you're not sure which port order to use, choose Top Down.
You can configure the ports on the gateway in this screen. Click on the Add a New Port box. In the Port Type field, select POTS. In the Port Number drop-down box, select the port number you’re adding. In the End Port Number drop-down box, select that same port number. It is important to add one port at a time in this fashion; selecting All Ports from the drop-down box when adding Analog Access gateway ports will result in voicemail integration failure.
Select Insert. A new screen will appear. Leave all parameters at their default setting, except for Call Restart Timer. Enter 1234 as the value for this parameter. This will allow CallManager to provide a positive disconnect signal to the Octel 250 port. Click Update and Close. Repeast these last steps to add all remaining ports on the gateway. Do not configure a DN (Directory Number) for these ports, as they will be configured later into a Route Group and associated with a Route Pattern.
? Add a Route Group comprised of analog ports assigned to voicemail.
After all the required Analog Station Gateway ports have been added, select Route Plan. Click on Route Group.
In the Route Group Name field, enter a descriptive name, such as SJ-voicemail, Vmail, etc.
Click Continue. In Device Name drop-down box, select the newly configured gateway(s). In the Port drop-down box, select port 1. In the Order drop-down box, select 1. Click Insert. To add subsequent ports, click Add Device, and follow the steps above. In the Port and Order drop-down boxes, select 2 for port 2; select 3 for port 3; and so on. Do not select “All” when adding gateway ports to the Route Group, as this will result in voicemail integration failure.
Click Finish.
? Add the Route Group to a Route List.
Although not necessary for proper integration, adding the newly created Route Group to a Route List will make administration simpler, specially when multiple gateways are used for connectivity to the Octel 250.
Select Route Plan. Select Route List. The Route List Configuration - New (step 1 of 1) screen is displayed. A Route List organizes a collection of Route Groups. The Order is the priority of each Route Group in the collection. The Order determines the progress of a search for available devices to select for a call. In the Route List Name box, enter a name for this Route List. It is once again recommended using a descriptive name, such as Vmail, Voicemail, SJ-vmail, etc.
Click Insert. Click Add Route Group. A new screen will appear. From the Select Route Group drop-down box, select the newly created Route Group. Click Add. A new screen will appear. Within this screen, you can add Calling/Called Party Transformation Masks, if required, pr leave all fields to their default settings. Click Insert. A feedback screen indicates the Route Group has been added to the Route List. Click Update. The Route Group you added will be displayed under the Route List.
? Add a Route Pattern.
Select Route Plan. Click Route Pattern.
The Route Pattern - New screen is displayed. In the Route Pattern box, type the Route Pattern, including numbers and wildcards (do not use spaces or dashes). In this case, the Route Pattern is the Octel 250 Access Number. This is the number subscribers will dial to access the Octel 250. This is also the number subscriber phones will be forwarded to for ring-no-answer and busy conditions.
In the Gateway/Route List drop-down box, select the newly created Route List. Uncheck Provide Outside Dial Tone. In the Discard Digits drop-down box, select <None>.
Click Update. The Route Pattern is now added.
? Configure the Cisco Messaging Interface.
Select Service. Select Cisco Messaging Interface.
In the Cisco Messaging Interface Configuration screen, click on a valid CallManager server, if one is already configured for CMI services. If no server has been configured for CMI, in the Select new server: drop-down box, select the CallManager server that will be used to provide the SMDI link to the Octel 250.
After a valid CallManager has been selected and entered, several parameters must be configured from proper SMDI link operation.
Select VoiceMailDn. Enter the Octel Access Number. Click Update.
Select SerialPort. Enter COM1 (default). Click Update. This COM port will connect to the Octel 250 Async port via the Lucent/OMD-provided RS-232 cable (P/N 057-1323-000) and a customer-provided DB25-to-DB9 connector.
Select BaudRate. Enter 9600 (default). Click Update.
Select Parity. Enter Even (default). Click Update.
Select DataBits. Enter 7 (default). Click Update.
Select StopBits. Enter 1 (default). Click Update.
The following parameters are optional and in the majority of cases will NOT require any modification:
“OutputDnFormat” – default “%010s”. This parameter allows you to “pad” the output string with a specified digit. In this case the “%” character is a formatting command. The character string “010s” tells CMI to format the SMDI message as a 10-digit string with leading “0”’s. e.g. In order to have CMI output a 7-digit string you would configure “OutputDnFormat” as “%07s”. The “s” simply tells CMI to output the result as a string.
“OutputExternalFormat” – default “%010s”. This parameter is used when you have a Voicemail system that is expecting a string “length” greater than the extension “length” on CallManager e.g. For a Voicemail system expecting a 7-digit string connected to a CallManager configured with 4-digit extensions you would configure “OutputExternalFormat” as “525%4s”. This would result in a string of “5251234” for extension 1234.
“InputDnSignificantDigits” – default “10”. In the case of our Voicemail system that is sending a 7-digit string for MWI commands to a CallManager system configured for 4-digit extensions, we would configure “InputDnSignificantDigits” = “4” e.g. We are keeping the “4” least significant digits.
Configuring the FXS ports on VG200 gateways
5.1 CONFIGURING CISCO VG200 PORTS
? Add the Analog ports in CallManager Administration. Open CallManager Administration.
Select Device. Select Add a New Device. Click Next.
Select Device Type. Select Gateway. Click Next. The Gateway - New screen is displayed. In the Gateway Type drop-down box, select Cisco VG200. Click Next.
In the MGCP Domain Name field, enter the host name as defined on the Cisco VG200 gateway. You must use the same value here that is used to configure the Cisco VG200 gateway at the IOS command line. In the Description field, enter a descriptive name for this device. Click Insert.
In the Module in Slot 1 drop-down box, select the module type installed in the VG200 to be configured. Click Insert.
In the VIC in Sub-Unit 0 drop-down box, select VIC-2FXS. In the VIC in Sub-Unit 1 drop-down box, select VIC-2FXS, if a second VIC module is used on the VG200. Click Update.
The gateway is now configured with 4 analog ports (Endpoint Identifiers). Click on the first port to be configured. In the Port Type drop-down box, select POTS. A new screen will appear. Select a valid Device Pool from the drop-down list. Leave all other parameters to their default settings. Click Insert.
Follow these steps to configure the additional VG200 ports.
? Once the ports have been added and assigned to a Route Group/Route List within CallManager Administration, you need to configure additional VG200 IOS parameters. Below is a sample IOS configuration of a Cisco VG200 gateway:
mgcp
mgcp call-agent 10.1.1.2
! IP Address of CallManager
mgcp dtmf-relay codec all mode out-of-band
mgcp ip-tos precedence 5
! Sets IP “Precedence” of RTP Stream to 5
mgcp default-package hs-package
ccm-manager switchback immediate
ccm-manager redundant-host 10.1.1.253
! Sets Backup CallManager – if applicable
ccm-manager mgcp
!
interface FastEthernet0/0
ip address 10.1.1.3 255.255.255.0
duplex auto
speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.1.1
! Default Route
no ip http server
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 1/1/1
!
dial-peer voice 100 pots
application MGCPAPP
port 1/0/0
!
dial-peer voice 101 pots
application MGCPAPP
port 1/0/1
!
dial-peer voice 102 pots
application MGCPAPP
port 1/1/0
!
dial-peer voice 103 pots
application MGCPAPP
port 1/1/1
!
end
6.0 CONFIGURING THE OCTEL SYSTEM
Configuring the Octel system
Menu 1.1:
• PBX type: 3 - Centrex #1AESS full duplex
• Number of Digits in Extension (used for Outcalling and ECP): set to mailbox length
• Number of Digits in Extension (used for Message Waiting): 10
NOTE: Cisco CallManager requires 10-digit extensions for MWI
Menu 4.1:
• Extension/Phone No.: Enter the two-digit link number (see following Table) followed by the Message Desk number , followed by the LTN (Logical Terminal Number) of each analog line that is plugged into each particular port. This field must contain a 9-digit number, with the following format:
LLGGGMMMM
LL = Physical Link Number
GGG = Message Desk (DCC) number (always 000)
MMMM = Logical Terminal Number (0001 - 0128)
• Line Type: 35 Loop start
• M column: N for all ports
Menu 4.3:
Special RS-232 Message Waiting: Y



Menu 6.1:
• Flash On-hook time: 850 milliseconds
• Pause Time: 1000 milliseconds
• Dialing Sequence to Transfer a Call: FPN
• Dialing Sequence to Reconnect a Call:
Ring No Answer: F
Busy: F
NOTE: Verify these dialing sequences for your PBX.
Menu 6.5 - Integration Link Management
• Link Number: (1-3)
• Link Name:
Type of Switch to which the System is Integrated: 3 - 1A ESS/SMDI, Full Duplex
Baud Rate: 3 - 9600 Baud
Number of Data Bits: 0 - 7 Data Bits
Number of Stop Bits: 0 - 1 Stop Bits
Parity (None/Odd/Even): 2 - Even Parity
XON/XOFF: 1 - Ignore XON/XOFF
Carrier Detect: 1 - Carrier Detect Not Used
Extension to Check SMDI Message Waiting: Leave Blank
Max. Msg. Waiting Operations per second: 1
Switch Number to which this Link is Associated: 1
SMDI link down alarm threshold counter: 1
NOTE: After configuring the above menus, select Menu 6.5.5 to reset the integration link(s).
Menu 8:
• Subscriber’s Extension Number:
NOTE: The “Subscriber’s Extension” number should be configured with leading zeros plus the mailbox number. For example, mailbox 5001 will have a subscriber’s station number of 0000005001. The number must equal ten digits.
• Int. Link Number: Enter the physical link number which is associated with the subscriber’s CallManager PC.
7.0 INSTALLING THE DATA LINK
Install the RS-232 data link
? Octel Communications provides a cable to connect from the COM port on the Cisco CallManager PC to the Octel 250. Use Cable Part Number 057-1323-000 along with a DB25-to-DB9 connector. Connect the cable to the appropriate serial port on the CF board of the Octel 250. See Figure 1.
7.1 INSTALLING THE FLT CABLE
? Each FLT board supports up to eight analog voice ports. One 25-pair, amphenol cable is required for each FLT. Figure 2 shows the proper cable pin-out for each of the eight voice ports.

7.2 TESTING THE INSTALLATION
Steps for testing the integration when installation is complete
? Create two mailboxes associated with two test extensions. Record a name and personal greeting for each mailbox.
? Call forward the test extensions to the Octel System Access Number.
? Using one test extension, call the other test extension. You should hear the personal greeting.
? Leave a message. Verify that the message waiting indicator turns on.


? Verify that transfer to attendant works properly.
? Call the Octel 250 from a test extension. You should hear the recorded name and be asked to enter the password.
? Review the message in the mailbox. Verify that the direct reply feature works by pressing 8 at the end of the message.
? Delete the message. Verify that the message-waiting indicator turns off.
Important notes regarding this integration
8.0 CONSIDERATIONS
8.1 Cisco CallManager does not support supervised transfers. Transfers on this switch can only be performed in a non-supervised mode, as the Cisco CallManager will release the call from the transferring station as soon as the last valid digit is dialed. Because of this, Automated Attendant and all ECP applications requiring transferring of calls must be configured for non-supervised transfers.
8.2 Cisco VG200 gateways do not support FAX transmission to/from subscribers mailboxes.








©2001 AVAYA Inc. All rights reserved. All trademarks identified by the ®, SM and TM are registered trademarks, servicemarks or trademarks respectively. All other trademarks are properties of their respective owners. The above information is based on knowledge available at the time of publication and is subject to change without notice. Printed in U.S.A.


AVAYA Inc.
1001 Murphy Ranch Road
Milpitas, CA 95035-7912
(408) 321-2000

http://www.avaya.com

Ken Means

http://www.tel-is.com

 

[KenMeans]

One way to test is to hook a PC to the port and see if you are
getting anything out of the call manager. then you can hook it to the octel and send a string of text to the port and see if it shows in the TDC

Ken Means

http://www.tel-is.com

 

[HmmG3]

The SMDI interface is coming from the VG248, not the CCM (it's in another room). The VG248 has an RJ45 connection on it for this. I was going back through the documentation I have for VG248/Octel250 integration and it says to use Cisco P/N 74-0495-01. A Google search shows it's the wrong gender, but I may break down and buy one.

If I could find out the pinout on the VG248, I could just make an adaptor myself using your other post on the async pinout. At least I know I have a hardware problem since the Octel isn't receiving the data.

Thanks,
Chris

 

[KenMeans]

I have never seen it done like that it has always been done on our jobs from the com port on the call manager

Ken Means

http://www.tel-is.com