Networking Octel OV250

[rod1248]

I am about to start a networking project that will entail networking 4 OV250 Octels and 1 Modular Messaging system using a Message Networking Server. The customer would like the Message networking server to handle all network calls with out a node (they want to be able to dial 4 digits to network to anyone one the campus). My question is, is there a way to set up the octels to automatically route the calls through the MN server regardless of where they are sending the message without the use of a node number? Or is the only way to accomplish this by creating the same node on all the octels that would send the call to the Message networking server and let that machine figure out where the calls need to go? Any thoughts?

Ray...

 

[KenMeans]

You must setup a node for the message networking system in the Octels. There is no other way to network them together. Is this an S3210 Or a 3400 message networking system. I am asking because on a S3210 you need to have a Bridge for every system you want to hook to it and send and receive messages. If you have the S3400 then you have 500 bridges.

I would just use the message networking to tie in the modular messaging into the other systems.

I can help if you have never done this before.

Ken Means

http://www.tel-is.com

 

[rod1248]

Ken,

Thanks for your response and your offer to help, the system is a MN3210. Can you expand in what you mean by setting up a bridge?

I was thinking we where going to have to use a node to do this but the customer did not want to add the extra digit if they didn't have to. I will keep you in mind if we run into a snag or just can't figure it out.

Ray

 

[KenMeans]

a bridge is a software bride in the S3210. If you have 50 Octels and 1 MMA system you would only need 1 bridge. The MMA system would be set to bridged system yes and then it can send and receive from any other system that is connected to the Message networking system.

But if you want to use the message networking system to do all of the networking VIA the message networking system you will need to have 51 bridged systems.

As far as the extra digit goes do all of the octels and the MMA system use the same length for the mailbox? and if so as long as there is not a conflict you should not have to use an extra digit.

Have you ever installed one before ?

Ken Means

http://www.tel-is.com

 

[rod1248]

Ok that makes sense, so since I have 4 Octels and 1 MM system then I would need 5 bridges built on the MN server to get it to work. What would need to be set up in the octels to get this to work? In other words with networking in the octels we use the open trees number to point the node to tell the system where to deposit the message, does that work the same for the MN server? The systems all use 4 digit extensions no extension is repeated in any of the other servers however the ranges are mixed throughout.

I've set up networking on the octel before but never on with using a MN server.

Ray

 

[KenMeans]

Do you know how many bridges were purchased with the system? I also assume that you are using digital networking ?

Octel 1 mb 1000 1499 node to S3210 is setup as 15 + 2 ,16 +2, 17 + 2, 18 + 2, 19 + 2, 2 + 3, 3 + 3, 4 + 3, 5 + 3, 8 + 3
Octel 2 mb 1501 1999
Octel 3 mb 2001 2500
Octel 4 mb 2501 5000

MMa system mb 8000 8999 none needed as it uses numeric addressing from the S3210

I think we should talk


Ken Means

http://www.tel-is.com

 

[rod1248]

Ok, I think I still have your number I will be in touch.

Thanks for your help.
Ray

 

[ChuckRCT]

Just a comment. A networking project with Octel systems and an MM system using the Message Networking S3210 requires a lot of planning prior to actually doing the networking. There are a lot of details involved with the process and it can be complex to setup.

As Ken Means has mentioned, the bridge setup is the way to go with this project.

 

[joeOctel]

The Aria Domain feature would allow you to address messages to other Octel's without a node number as long as you have digital networking and none of the extensions overlap in the other systems. I don't think you can use this feature with the S3210, but I have never tried.

 

[rod1248]

We are going ahead with the networking, on the MN3210 it is asking for the System Mailbox ID of the octels. Anyone know what it is referring to?


Ray

 

[KenMeans]

put in the system manager MB

Ken Means

http://www.tel-is.com

 

[rod1248]

Should the system manager mailbox in the octel be setup differently or have it's own class of service? The MN is attempting to pull information from the octels and there is an error message that the "download failed due to mailbox error". Does this make sense?

Ray.

 

[KenMeans]

well it may but i am not sure do you have updates in and out set to yes on the node profile ? in the s3210

Ken Means

http://www.tel-is.com

 

[KenMeans]

can you post the message you are getting and are you using Analog networking ?

Ken Means

http://www.tel-is.com

 

[rod1248]

Ken,
Here is what we are getting and yes this is Analog networking we are trying to set up.

12/13/05 09:16:20 OG ONG065 1ADM:Name Pull Updates Failed - Miner; Aborted at Mbx
12/13/05 09:16:51 LP 1 Starting full update from VMMSS1.
12/13/05 09:16:56 LP 1 Full update completed with errors from VMMSS1.
12/13/05 09:18:04 OG ONG064 1 ADMelta Updates Started - Miner
12/13/05 09:18:08 OG ONG064 1 ADMelta Updates Started - Facilities
12/13/05 09:18:16 OG ONG065 1 ADMelta Updates Failed - Facilities; Aborted at Mbx
12/13/05 09:18:20 OG ONG065 1 ADMelta Updates Failed - Miner; Aborted at Mbx
12/13/05 09:33:04 OG ONG064 1 ADMelta Updates Started - Facilities
12/13/05 09:33:08 OG ONG064 1 ADMelta Updates Started - Miner
12/13/05 09:33:12 OG ONG065 1 ADMelta Updates Failed - Facilities; Aborted at Mbx
12/13/05 09:33:23 OG ONG065 1 ADMelta Updates Failed - Miner; Aborted at Mbx
12/13/05 09:48:04 OG ONG064 1 ADMelta Updates Started - Miner
12/13/05 09:48:08 OG ONG064 1 ADMelta Updates Started - Facilities
12/13/05 09:48:16 OG ONG065 1 ADMelta Updates Failed - Facilities; Aborted at Mbx
12/13/05 09:48:20 OG ONG065 1 ADMelta Updates Failed - Miner; Aborted at Mbx
12/13/05 10:03:04 OG ONG064 1 ADMelta Updates Started - Facilities
12/13/05 10:03:08 OG ONG064 1 ADMelta Updates Started - Miner
12/13/05 10:03:12 OG ONG065 1 ADMelta Updates Failed - Facilities; Aborted at Mbx
12/13/05 10:03:23 OG ONG065 1 ADMelta Updates Failed - Miner; Aborted at Mbx
12/13/05 10:18:06 OG ONG064 1 ADMelta Updates Started - Facilities
12/13/05 10:18:12 OG ONG064 1 ADMelta Updates Started - Miner
12/13/05 10:18:14 OG ONG065 1 ADMelta Updates Failed - Facilities; Aborted at Mbx
12/13/05 10:18:28 OG ONG065 1 ADMelta Updates Failed - Miner; Aborted at Mbx

Thanks so much for your help.
Ray

 

[KenMeans]

Do you have a mailbox in the profile of the node on the s3210 for the system mailbox ?

Ken Means

http://www.tel-is.com

 

[rod1248]

Yes there is a mailbox in the node profile on the 3210.

Ray

 

[KenMeans]

try just putting a user mailbox number in it.

Ken Means

http://www.tel-is.com

 

[KenMeans]

if you can post a screen shot of the node in the miner system

Ken Means

http://www.tel-is.com

 

[rod1248]

Here you go:

- Octel Network Administration -
- Node Profile -

Node Number: 1 Node Name: MN3210
Transmission Type: 0 - Normal Node Type: 0 - Octel Analog
Number of Digits in a Mailbox: 4 Serial Number: 80000
NameNet Type: 2 - Usage-based Site ID:
NameSend: 3 - Send And Receive
Phone Number: 1620 Ext:
Dialing Sequence: N Authorization Code:
Access Type: 0 - Direct Dial Country: 1 - North American
Max Simultaneous Analog Transmissions: 1 Threshold: 0 msgs, 0 mins

IP Address: 0.0.0.0 Fallback: 0 - None
Name Transmission Allowed: Y Play Node Name: Y
ASCII Name Check: 1 - Check All Msgs Node Response Allowed: Y

System Manager Name: Mailbox Number:
System Manager Phone Number: Ext:


- Octel Network Administration -
- Node Profile -

Node Number: 1 Node Name: MN3210

Weekday Message Delivery Window 1
Begin: 12:00A Interval: 0 - Immediate
End: 11:59P Priority: 0 - Non-Urgent/Standard Subscriber
Weekday Message Delivery Window 2
Begin: 12:00A Interval: 0 - Immediate
End: 12:59P Priority: 1 - Urgent/Standard Subscriber
Weekday Message Delivery Window 3
Begin: 12:00A Interval: 0 - Immediate
End: 11:59P Priority: 2 - Non-Urgent/Priority Subscriber
Weekday Message Delivery Window 4
Begin: 12:00A Interval: 0 - Immediate
End: 11:59P Priority: 3 - Urgent/Priority Subscriber
Weekday Message Delivery Window 5
Begin: 12:00A Interval: 0 - Immediate
End: 11:59P Priority: A - Administrative Messages

- Octel Network Administration -
- Node Profile -

Node Number: 1 Node Name: MN3210

Weekend/Holiday Message Delivery Window 1
Begin: 1:00A Interval: 0 - Immediate
End: 11:00P Priority: 0 - Non-Urgent/Standard Subscriber
Weekend/Holiday Message Delivery Window 2
Begin: Interval:
End: Priority:
Weekend/Holiday Message Delivery Window 3
Begin: Interval:
End: Priority:
Weekend/Holiday Message Delivery Window 4
Begin: Interval:
End: Priority:
Weekend/Holiday Message Delivery Window 5
Begin: Interval:
End: Priority:


- Octel Network Administration -
- Node Profile -

Node Number: 1 Node Name: MN3210

PREFIX D PREFIX D PREFIX D PREFIX D PREFIX D
---------- - ---------- - ---------- - ---------- - ---------- -
2 4