Re: [cisco-voip] Mediasense Replacement

[Ki Wi]

Thanks guys! Will reach out to them.



On Tue, Apr 18, 2017 at 6:37 AM, Dana Tong  wrote:

> This is correct. It’s based upon CentOS. And quite cost effective.
>
>
>
> *From: *cisco-voip  on behalf of Doug
> Anderson 
> *Date: *Tuesday, 18 April 2017 at 1:44 am
> *To: *Anthony Holloway , Ki Wi <
> kiwi.vo...@gmail.com>, "cisco-voip@puck.nether.net" <
> cisco-voip@puck.nether.net>
> *Subject: *Re: [cisco-voip] Mediasense Replacement
>
>
>
> If memory serves Zoom is linux-based.
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Anthony Holloway
> *Sent:* Monday, April 17, 2017 10:40 AM
> *To:* Ki Wi; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] Mediasense Replacement
>
>
>
> If you have access to the MediaSense EoL FAQ page
> ,
> you'll see alternatives listed.  I don't have experience with any linux
> based solutions.
>
>
>
> On Mon, Apr 17, 2017 at 12:50 AM Ki Wi  wrote:
>
> Hi Group,
>
> Since Mediasense have announced EoS. Is there any Linux based voice
> recording system in the market?
>
>
>
>
>
> --
>
> Regards,
>
> Ki Wi
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>
>


-- 
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Mediasense Replacement

[Dana Tong]

This is correct. It’s based upon CentOS. And quite cost effective.

From: cisco-voip  on behalf of Doug 
Anderson 
Date: Tuesday, 18 April 2017 at 1:44 am
To: Anthony Holloway , Ki Wi 
, "cisco-voip@puck.nether.net" 

Subject: Re: [cisco-voip] Mediasense Replacement

If memory serves Zoom is linux-based.

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Anthony Holloway
Sent: Monday, April 17, 2017 10:40 AM
To: Ki Wi; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Mediasense Replacement

If you have access to the MediaSense EoL FAQ 
page,
 you'll see alternatives listed.  I don't have experience with any linux based 
solutions.

On Mon, Apr 17, 2017 at 12:50 AM Ki Wi 
mailto:kiwi.vo...@gmail.com>> wrote:
Hi Group,
Since Mediasense have announced EoS. Is there any Linux based voice recording 
system in the market?



--
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Mediasense Replacement

[Doug Anderson]

If memory serves Zoom is linux-based.

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Anthony Holloway
Sent: Monday, April 17, 2017 10:40 AM
To: Ki Wi; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Mediasense Replacement

If you have access to the MediaSense EoL FAQ 
page,
 you'll see alternatives listed.  I don't have experience with any linux based 
solutions.

On Mon, Apr 17, 2017 at 12:50 AM Ki Wi 
mailto:kiwi.vo...@gmail.com>> wrote:
Hi Group,
Since Mediasense have announced EoS. Is there any Linux based voice recording 
system in the market?



--
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Mediasense Replacement

[Anthony Holloway]

If you have access to the MediaSense EoL FAQ page
, you'll see alternatives
listed.  I don't have experience with any linux based solutions.

On Mon, Apr 17, 2017 at 12:50 AM Ki Wi  wrote:

> Hi Group,
> Since Mediasense have announced EoS. Is there any Linux based voice
> recording system in the market?
>
>
>
> --
> Regards,
> Ki Wi
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] PCD cluster discovery problem

[Anthony Holloway]

Dang.  Thanks for posting your resolution.  And how is that even a problem
in 2017?

Or case sensitive hostnames?  I'm looking at you UCCX!

On Sun, Apr 16, 2017 at 5:59 PM Ahmed Abd EL-Rahman <
ahmed.rah...@bmbgroup.com> wrote:

> Just for the record, I have fixed the issue which was very weird.
>
> Simply the password of the PCD was apparently too complex for the
> application to work properly, so when I re-installed the PCD again using a
> simpler password (for the admin and platform account) everything went
> smooth.
>
>
>
>
> BR
> Ahmed Abd EL-Rahman
> Senior Network Engineer
>
> Sent from my iPhone
>
> On Apr 16, 2017, at 2:39 PM, Ahmed Abd EL-Rahman <
> ahmed.rah...@bmbgroup.com> wrote:
>
> Dear Gents,
>
> I’m trying to use PCD to migrate CUCM cluster from version 8.6 to 11.5, I
> did it with the same exact versions of all PCD, old CUCM and new CUCM and
> it worked just fine in one location, but when I’m trying to do the same in
> the current cluster the first step which is PCD discovery of the old CUCM
> cluster always fail with an error “login failed” as shown:
>
> [cid:image001.png@01D2B6BE.C0C7B280]
>
> I tried later and installed the ciscocm.ucmap_platformconfig.cop file
> manually on both CUCM servers but result remains the same!!
>
> I check the PCD logs and found the following:
> “”””
> CALLING ucmapLib::getFile {exp3 install platformConfig.xml PCD IP Address
> adminsftp /export/platformConfig/temp/}
> FAILED ucmapLib::getFile, not valid username/password for sftp
> 2017-04-16 13:31:15,929 INFO  [DefaultQuartzScheduler_Worker-3]
> inventory.Migration.nodeDiscovery - downloadFile errorCode 123
> 2017-04-16 13:31:15,929 INFO  [DefaultQuartzScheduler_Worker-3]
> inventory.NatAddressHelper.getPublicIP - Application Node private IP
> Address is : 172.16.65.251
> 2017-04-16 13:31:15,929 INFO  [DefaultQuartzScheduler_Worker-3]
> inventory.Migration.nodeDiscovery - Return nodeDiscovery result 123
> 2017-04-16 13:31:15,929 INFO  [DefaultQuartzScheduler_Worker-3]
> scheduler.CustomJob.acquireLock - T77:TA78:N71 waiting for DB lock
> 2017-04-16 13:31:15,929 INFO  [DefaultQuartzScheduler_Worker-3]
> scheduler.CustomJob.acquireLock - T77:TA78:N71 acquired lock
> 2017-04-16 13:31:15,933 INFO  [DefaultQuartzScheduler_Worker-3]
> db.EntityBroker.updateNodeInfo - Updated 71 to v3
> 2017-04-16 13:31:15,933 INFO  [DefaultQuartzScheduler_Worker-3]
> scheduler.CustomJob.releaseLock - T77:TA78:N71 releasing DB lock
> 2017-04-16 13:31:15,933 INFO  [DefaultQuartzScheduler_Worker-3]
> scheduler.DiscoveryJob.executeJob - discovery node 71 failed with errorcode
> 123 as it is Failed to download 'PlatformConfig.xml' from the node
> CUCM_PUB_IP_Address  to sftpServer PCD IP Address
>
> “
> Here is the exact version used:
> Old CUCM: 8.6
> PCD: 11.5(3)
> New CUCM: 11.5(1)SU2
>
> So any clues to solve this issue ??
>
>
>
>
>
>
>
> Best Regards
>
> Ahmed Abd EL-Rahman
> Senior Network Engineer
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip