Contact Store Separate server VMpro on Linux (UCMODULE) issue 1

[VikeshR]

Hi all help please.
I installed ContactStore on windows server and my VMPRO is on the c110 UC module. Ilogged into the root and found that the calls are going to the VRL.opt/vmpro/VRL
No the problem is
1. getting contact store to see the folder on the uc module
2. making sure that the folder on the UC module (Linux) is is visible as a network share from the ContactStore server.
I get a warning on Contact store "No Voice Recording Library Path found" Check the VMPRO installation configuration.

Can some one please assist. Do you think i need to install the samba on the uc module (or can I do something else)

 

[tlpeter]

Then it is already stoppen so don't worry.
Then you can skip this step.

BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

okay cool.

 

[RogerTurboFederer]

@ tlpeter

Thanks a lot.

Did you make any changes ? Are there on the FAQ ?

 

[RogerTurboFederer]

Have a nice pink day.

 

[tlpeter]

I did nake a change indeed.
The code is now:

cd /home/webcontrol
wget [URL unfurl="true"]http://ista.home.xs4all.nl/ipoffice/AvayaLinuxSharing/UCM8_0/CentOS-Base.repo[/URL]
wget [URL unfurl="true"]http://ista.home.xs4all.nl/ipoffice/AvayaLinuxSharing/UCM8_0/smb.conf[/URL]
wget [URL unfurl="true"]http://ista.home.xs4all.nl/ipoffice/AvayaLinuxSharing/UCM8_0/windows-sharing-8.0.20-11.noarch.rpm[/URL]
cp CentOS-Base.repo /etc/yum.repos.d
cp windows-sharing-8.0.20-11.noarch.rpm /var/cache/avaya/apps
yum install samba samba-swat -y
cd /etc/yum.repos.d
rm CentOS-Base.repo -f
cd /var/cache/avaya/apps
rpm -ivh windows-sharing-8.0.20-11.noarch.rpm
cd
service smb stop
cd /etc/samba
rm smb.conf -f
cd
cd /home/webcontrol
cp smb.conf /etc/samba
service smb start
chkconfig smb on
chmod 777 /opt/vmpro/VRL

BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

I did manage to create a share drive and I can now see the files on \\.......\vrl
Contact store still complains about "No voice Recording Library Found"
Did you test yours and does it work?

 

[tlpeter]

You need to tell on the CS server where the recordings are.

This is from the installation doc:

4. If ContactStore is to be installed on a separate machine from the Voicemail Pro server:
1. Check that the Voice Recording Library folder (by default c:\Program Files\Avaya\IP Office\Voicemail
Pro\VM\VRL) on the Voicemail Pro server is visible as a network share from the ContactStore server.
2. Configure your security so that the ContactStore service can read and write to the share for that folder.
3. Create and set a registry key on the ContactStore server to tell ContactStore the location of the share. Set
the key HKEY_LOCAL_MACHINE\SOFTWARE\Network Alchemy\Voicemail\Directories\VRLDir to
be a string containing the name of the share.

BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

I did that already !! Still no luck
I even mapped a path and used the mapped drive in the registry string

 

[tlpeter]

This should work as the files are accessable on the share.
Do you have recordings in the share?
Did you reboot the CS server after the regedit?


BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

Yes there are .wav and txt files in the folder.
I rebooted the CS as well. Im now going to re-install CS and see what happens. Its strange that ist now visble but CS is not picking it up or I have configured the string wron. Im using windows server 2008 64bit.

 

[VikeshR]

tell me under the modify string I paste this in : \\ipaddress\vrl?

 

[tlpeter]

I have gotten this from Avaya a while back for a 64bit OS:

If you have a 64 bit O/S open an explorer window and navigate to C:\Windows\sysWOW64 and find the file call regedit in that directory and run it. As above for the 32 bit system you need to create the same entry in the registry.


See if that fixes your issue.


BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

Checking....nope no luck

 

[tlpeter]

Then i think you need to find logs on the CS why it does not work.
It will be guessing from my side

You could try this:

Change the smb.conf and set only these lines for the VRL

[VRL] # name of share
path = /opt/vmpro/VRL
public = Yes
writeable = Yes
guest ok = Yes

Everything else can be removed.


BAZINGA!

I'm not insane, my mother had me tested!

 

[kholladay]

@tlpeter while I appreciate all of the hard work you've done to uncover this solution I have to appeal to your intellect here. You are giving a solution for a completely unsupported feature to a person who didn't even bother to read the documentation telling him that it wasn't supported in the first place. Now he is going to run off and do this, granted with some success and then next you know he'll be right back here asking for support when it breaks. While your work is fantastic you haven't done him, you or this forum any favors by giving him this information. And in fact you have empowered him to go off and ignore the mistake he has already made and instead keep on doing the wrong thing over and over because now he knows he can.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[tlpeter]

Hi Kyle,

The first thing i did was telling him that it is not supported.
But the reason that it is not supported is only a security reason.
But yes you are right but it can be done without issues.
We have run the UCM for the whole trial with the share enabled.
I really do not understand that this is not supported.
Avaya wants the Linux stuff simple and that is a reason that it is not there yet.
It should not be that hard to put in to the webcontrol page.


BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

Kholladay, kindly refrain from assumptions and making statements without proof. Firstly I had read the documentation and was aware that Linux is not supported, Being new to IP office and using the extremely vague Avaya manuals with the IP office support im my country, we were told that its not supported on any linux OS so a separate windows server will work.(get it?)
Secondly the forums are here to assist, and I appreciate greatly how TLPeter assisted me. There forums are here to assist and I will contribute as I go along, so if you not willing to assist fellow users and contribute instead of making improper statements I suggest you leave the forum if you now happy.
TLPeter thanks again.

 

[kholladay]

Then I'll withdraw my complaint, cap my frustration and offer an apology. If you have indeed done your due diligence and understand that while the actual use of ContactStore on Linux/UCM is supported by Avaya the manual configuration is up to you as is the ongoing support then by all means have at it.

I suppose that after over a decade of hard work, study, and time spent on testing solutions then documenting the results I have become jaded and frustrated with those seemingly too lazy to do the legwork on their own. If this is not the case then I welcome your questions.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[VikeshR]

Hi , I understand your frustrations there and realize the consequences of this solution, however this is a test or research on getting it to work on the Linux OS as a work around for customers wanting Linux and Windows. But thank you for responding.

 

[kholladay]

I wouldn't really call it a work around because the concept and end result itself are officially supported. It is all the stuff in the middle that you are left on your own to accomplish.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford