Message Networking and Cisco Unity

[ktludwig]

It's been a while since I've worked on Message Networking and I'm very new to Cisco. Has anyone ever set up networking between the 2 using VPIM? I think I've got it set up correctly but I can't send messages back and forth. I get an error in the Unity mailbox saying the message can't be delivered because of error "518" and I haven't been able to find anything that tells me what that error indicates.

I can't tell if my issue is with the Unity or the MN. I get the error message seconds after sending the message so my guess is the Unity is the source of the error but I can't confirm this and the configuration looks OK.

Any help understanding the error would be greatly appreciated.

Thanks!

 

[KenMeans]

what do you see in the log of the MNS ? Anything ?

You can send a test from the MNS to the Cisco to see if it receives it

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ktludwig]

Ken,

The MNS log shows an error "NO_AUTH_SND" Unknown originator.

 

[KenMeans]

then the mns is not setup right somewhere as it does not know who the cisco is

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ktludwig]

Thanks Ken. I will look at the set up again. Is this indicative with the remote machine setup or with the subscriber?

 

[KenMeans]

Hit may ne both but are you sure the remote user is in the dial plan range?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ktludwig]

Ken,

I did find an issue with the FQDN name and I'm getting a little further along but the message is still not reaching the recipient on the far end.

The message appears to be hitting the MNS and I get back a failure message from the MNS that includes the recorded name of the recipient on the far end. The error says the message can't be sent "due to sending restrictions". Obviously something is up on the MNS. I am investigating further. If you know what the issue is, I'm all ears.

I really appreciate your help.

 

[kepetersen]

Is Updates In & Out set to Y for the MN configuration that is pointing to the Cisco? Is the password passed between both units the same?

 

[ktludwig]

kpetersen,

The updates in and out appears only to apply to MNS nodes that are MM. There is no option for that on a VPIM node. I still can't get messages to go. When I send from MM to Unity, the message eventually get returned. But from Unity to MM, I have no idea what happens to the message. I sent a couple yesterday but they haven't been returned as of yet.

The odd thing is that when I address the message on MM I hear the recorded name of the mailbox on the Unity. So it makes no sense that I can get the name across, but not the message.

I don't see anything in the MNS logs that indicate an issue and I have no idea where the hell the messages I sent from Unity to MM went. They're not in the message queue in MNS.

 

[kepetersen]

So let me confirm the setup. It is going from a Cisco Unity to an Message Networking box and out to an MM?

Is this a new setup? Are other destinations through this MN working?

From the Mn to the MM is the Updates In/Out set to Yes on the MN and the MM?

 

[KenMeans]

So on the Cisco side you have checked all of the following ?


On the VPIM system:

Administer the Message Networking system as a VPIM network node on the VPIM system. You might need the following information, depending on your VPIM system type:

The fully qualified domain name and IP address of the Message Networking system. The VPIM system uses this information to send messages to the Message Networking system.
The Message Networking network address length.
The Message Networking network address ranges for other messaging systems in the network. Depending on the specific VPIM system, the address ranges that are required are generally the dial plan mapping entries for each remote machine on the Message Networking system. In other cases, you might need all digits of the address ranges. In addition to the dial plan map, you might need to add a prefix to address messages to the Message Networking system.
If you need to specify a server type, obtain this information from the VPIM system administrator.
If you need to specify a protocol type, select VPIM.

Note: The VPIM system must pass to Message Networking only those addressing digits used in the Message Networking network. When using telephones, subscribers on the VPIM system might have to dial additional digits to address messages to remote subscribers on the Message Networking network. This is sometimes referred to as a prefix. These digits might be required for the following reasons:

The VPIM system can identify the addressee as a remote subscriber.
The VPIM system can identify the remote system where the remote subscriber resides (in this case, the Message Networking system).

Do not administer the VPIM system to pass any other digits to the Message Networking system. Instead, administer the VPIM system so that it strips off these additional addressing digits when it passes the message to the Message Networking system. Only addresses within the ranges specified for Message Networking remote machines (specified in the Dial Plan Mapping) are to be sent to the Message Networking system.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[KenMeans]

if you send from mm to Unity does it go ? and if not what is the error in the MNS

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ktludwig]

Guys,

Thanks for all the help. I've discovered an issue with the FQDN on the Unity. Basically it's not defined. It only has the machine name where the FQDN name should be.

It's a production box so it's not something I can just change. It's going to take some planning.

I appreciate all your help and input.