Re: [cisco-voip] Voicemail history

[Haas, Neal]

1. What does your company want for a retention period for deleted VM. We 
started at 2 weeks, now I think we are 6 weeks.

2. for regulatory or legal requirements (state or local laws) what are those, 
we post on an MOU we only keep them for a specific period of time. If we have a 
request for anything outside of the MOU, we say we dont keep backups for that 
long.

3. do you use the integration to outlook? VM files will be kept under the 
outlook retention time also..

4. we have 6,000 VM boxes, our database size is 20 gig total, we set the VM box 
size to be small.


Neal Haas


From: cisco-voip  on behalf of Parker 
Pearson - Donoma 
Sent: Wednesday, September 6, 2017 8:13 PM
To: Ben Amick; Cisco VOIP
Subject: Re: [cisco-voip] Voicemail history

It really depends on whether you have regulatory or legal requirements to 
retain your voicemails.  Voicemails are an electronic record that can be 
requested for audits or legal discovery.

I understand the desire to groom out the messages in 21-30 days to keep the 
database humming along - but it has to be balanced with the possible need for 
retention & compliance.  A conversation across functions is probably a really 
good idea to find out what your stakeholders need too.

My understanding is that Unity Connection has a limit for VM storage - I think 
it's 2 TB. Depending on the size of your organization and how many voicemails 
your users are averaging in their mailboxes - that limit can get tight.   An 
easy option to satisfy both IT management & retention compliance is a solution 
like Message Vault.  Retains records as needed, enables a very short retention 
length that keeps your UCN database tidy.

Hope that helps.


[Donoma Software Web Page]

Parker Pearson
Vice President, Marketing & Business Development

Donoma Software
1750 Kraft Dr. Suite 1200 Blacksburg, VA 24060
540.443.3577
par...@donomasoftware.com
www.donomasoftware.com
[Facebook] [Twitter] 
  [LinkedIn] 



From: cisco-voip  on behalf of Ben Amick 

Date: Wednesday, September 6, 2017 at 10:18 PM
To: Cisco VOIP 
Subject: [cisco-voip] Voicemail history

So I was just wanting to reach out and see what everybody thinks is a 
reasonable unity message aging scheme? What point does it get to a point where 
you start having storage issues?
Ben Amick
Telecom Support Analyst

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material.  Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited.  If you received this 
in error, please contact the sender and destroy any copies of this information.




Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Voicemail history

[Anthony Holloway]

I rarely have set an aging policy different than the default.  I guess I'm
in the camp for just letting things fill up, and then let the system tell
the users to clean up their mailbox.

If I put a little thought into an aging policy, Single Inbox and other
fancy features aside, I think new messages should never age, and read
messages should age to deleted after 2 weeks, then deleted should go the
way of the dodo after 1 week.  This allows users to keep a message around
for an arbitrary amount of time, again with no fancy features, by
re-marking the message as unread after they listen to it.  They get the
small burden of having that MWI light on, and on devices without message
counts, that can be a pain.

On Wed, Sep 6, 2017 at 9:18 PM Ben Amick  wrote:

> So I was just wanting to reach out and see what everybody thinks is a
> reasonable unity message aging scheme? What point does it get to a point
> where you start having storage issues?
>
> Ben Amick
> Telecom Support Analyst
>
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you ___
> 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] Voicemail history

[Parker Pearson - Donoma]

It really depends on whether you have regulatory or legal requirements to 
retain your voicemails.  Voicemails are an electronic record that can be 
requested for audits or legal discovery.

I understand the desire to groom out the messages in 21-30 days to keep the 
database humming along – but it has to be balanced with the possible need for 
retention & compliance.  A conversation across functions is probably a really 
good idea to find out what your stakeholders need too.

My understanding is that Unity Connection has a limit for VM storage – I think 
it’s 2 TB. Depending on the size of your organization and how many voicemails 
your users are averaging in their mailboxes – that limit can get tight.   An 
easy option to satisfy both IT management & retention compliance is a solution 
like Message Vault.  Retains records as needed, enables a very short retention 
length that keeps your UCN database tidy.

Hope that helps.


[Donoma Software Web Page]

Parker Pearson
Vice President, Marketing & Business Development

Donoma Software
1750 Kraft Dr. Suite 1200 Blacksburg, VA 24060
540.443.3577
par...@donomasoftware.com
www.donomasoftware.com
[Facebook] [Twitter] 
  [LinkedIn] 



From: cisco-voip  on behalf of Ben Amick 

Date: Wednesday, September 6, 2017 at 10:18 PM
To: Cisco VOIP 
Subject: [cisco-voip] Voicemail history

So I was just wanting to reach out and see what everybody thinks is a 
reasonable unity message aging scheme? What point does it get to a point where 
you start having storage issues?
Ben Amick
Telecom Support Analyst

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material.  Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited.  If you received this 
in error, please contact the sender and destroy any copies of this information.




Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] Voicemail history

[Ben Amick]

So I was just wanting to reach out and see what everybody thinks is a 
reasonable unity message aging scheme? What point does it get to a point where 
you start having storage issues?

Ben Amick
Telecom Support Analyst




Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OT: Add move change

[Lelio Fulgenzi]

Thanks Stephen!

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: Stephen Welsh [mailto:stephen.we...@unifiedfx.com]
Sent: Wednesday, September 06, 2017 3:16 PM
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OT: Add move change

Hi Lelio,

Kinda, you may still need to know the AXL data structure, however you don’t 
have to learn the CUCM Data Dictionary as the AXL models effectively ‘flatten’ 
the raw tables. Also it is a full CRUD interface, with a simple PUT operation 
you can update just part of phone record (i.e. description, Device pool). You 
can even copy a resource, i.e.

GET /AutomationFX/api/AXL/phone/SEP0001

Then submit the returned AXL model as a POST request to create a new/copy using 
a POST operation:

POST /AutomationFX/api/AXL/phone/SEP0002

Because it has a live testing interface you can perform live queries against 
CUCM to see what the data/model looks like. The interactive testing interface 
is there to test/learn the REST api, so that you can then create a 
script/application that could perform those operation in bulk, or as part of an 
existing application etc.

Ultimately this is designed to enable simple development against CUCM so anyone 
with general web development skills can easily create applications 
(provisioning, testing etc) against CUCM in a similar way that you can do with 
Cisco Spark.

We shall be posting a number of example scripts/application on the git hub site 
over the next few months before we launch. So the purpose of AutomationFX may 
be a bit abstract until we share some concrete examples.

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 19:06, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:

Hi Stephen,

Does this act a bit like a sandbox tool where I don’t have to learn the AXL 
library but use a GUI front end to do stuff and it makes the calls 
appropriately?

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: Stephen Welsh [mailto:stephen.we...@unifiedfx.com]
Sent: Wednesday, September 06, 2017 1:33 PM
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OT: Add move change

Hi,
Co-incidentally we (UnifiedFX) are due to launch something that may be relevant 
called AutomationFX. It basically exposes CUCM API’s (i.e. AXL & CTI) via REST. 
You can call the REST API locally or via our ‘CloudFX’ connection from a secure 
cloud endpoint.

If you have a read over the following page it outlines what AutomationFX can do:

https://github.com/unifiedfx/awesome-automationfx

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 17:13, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:

The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cis

Re: [cisco-voip] OT: Add move change

[Stephen Welsh]

Hi Lelio,

Kinda, you may still need to know the AXL data structure, however you don’t 
have to learn the CUCM Data Dictionary as the AXL models effectively ‘flatten’ 
the raw tables. Also it is a full CRUD interface, with a simple PUT operation 
you can update just part of phone record (i.e. description, Device pool). You 
can even copy a resource, i.e.

GET /AutomationFX/api/AXL/phone/SEP0001

Then submit the returned AXL model as a POST request to create a new/copy using 
a POST operation:

POST /AutomationFX/api/AXL/phone/SEP0002

Because it has a live testing interface you can perform live queries against 
CUCM to see what the data/model looks like. The interactive testing interface 
is there to test/learn the REST api, so that you can then create a 
script/application that could perform those operation in bulk, or as part of an 
existing application etc.

Ultimately this is designed to enable simple development against CUCM so anyone 
with general web development skills can easily create applications 
(provisioning, testing etc) against CUCM in a similar way that you can do with 
Cisco Spark.

We shall be posting a number of example scripts/application on the git hub site 
over the next few months before we launch. So the purpose of AutomationFX may 
be a bit abstract until we share some concrete examples.

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 19:06, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:


Hi Stephen,

Does this act a bit like a sandbox tool where I don’t have to learn the AXL 
library but use a GUI front end to do stuff and it makes the calls 
appropriately?

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: Stephen Welsh [mailto:stephen.we...@unifiedfx.com]
Sent: Wednesday, September 06, 2017 1:33 PM
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OT: Add move change

Hi,
Co-incidentally we (UnifiedFX) are due to launch something that may be relevant 
called AutomationFX. It basically exposes CUCM API’s (i.e. AXL & CTI) via REST. 
You can call the REST API locally or via our ‘CloudFX’ connection from a secure 
cloud endpoint.

If you have a read over the following page it outlines what AutomationFX can do:

https://github.com/unifiedfx/awesome-automationfx

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 17:13, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:

The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

___
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] OT: Add move change

[Lelio Fulgenzi]

Hi Stephen,

Does this act a bit like a sandbox tool where I don’t have to learn the AXL 
library but use a GUI front end to do stuff and it makes the calls 
appropriately?

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: Stephen Welsh [mailto:stephen.we...@unifiedfx.com]
Sent: Wednesday, September 06, 2017 1:33 PM
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OT: Add move change

Hi,
Co-incidentally we (UnifiedFX) are due to launch something that may be relevant 
called AutomationFX. It basically exposes CUCM API’s (i.e. AXL & CTI) via REST. 
You can call the REST API locally or via our ‘CloudFX’ connection from a secure 
cloud endpoint.

If you have a read over the following page it outlines what AutomationFX can do:

https://github.com/unifiedfx/awesome-automationfx

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 17:13, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:

The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

___
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] OT: Add move change

[Charles Goldsmith]

Scott, sounds like you are looking for something to notify you when changes
are made.  Variphy does this well with their snapshot compare.  Compare can
look at different snapshots and compare the difference, or compare a
snapshot to current in CUCM.

Not associated with Variphy, other than a happy customer.

On Wed, Sep 6, 2017 at 10:09 AM, Scott Voll  wrote:

> What do other use for add, moves and changes to there environments?
>
> We have a home grown app that is not working well, to notify Telecom group
> about changes to the phones, new users, configuration changes, etc.
>
> Does anyone know of any can'd or cloud based software?  Are there any that
> interface with Cisco to automate the process via AXL / SOAP?
>
> Just putting my feelers out to see what is available.
>
> Thanks
>
> Scott
>
>
> ___
> 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] OT: Add move change

[Terry Oakley]

And I will add that as a user of their (UnifiedFX) platform MigrationFX we have 
successfully migrated many devices without losing any settings or associations 
even putting in associations such as rtapi configs.   I would highly recommend 
this product as it simplifies and hastens the deployment of new end devices 
without compromising your setups.  It also tags the previous device at that 
port or will remove it from your UC environment.Brilliant product and 
looking forward to their next gem.

Terry Oakley
Telecommunications Coordinator
Red Deer College
Sent from my BlackBerry — the most secure mobile device — via the TELUS Network
From: stephen.we...@unifiedfx.com
Sent: 6 September 2017 11:33 a.m.
To: le...@uoguelph.ca
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OT: Add move change


Hi,
Co-incidentally we (UnifiedFX) are due to launch something that may be relevant 
called AutomationFX. It basically exposes CUCM API’s (i.e. AXL & CTI) via REST. 
You can call the REST API locally or via our ‘CloudFX’ connection from a secure 
cloud endpoint.

If you have a read over the following page it outlines what AutomationFX can do:

https://github.com/unifiedfx/awesome-automationfx

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 17:13, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:


The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

___
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] OT: Add move change

[Stephen Welsh]

Hi,
Co-incidentally we (UnifiedFX) are due to launch something that may be relevant 
called AutomationFX. It basically exposes CUCM API’s (i.e. AXL & CTI) via REST. 
You can call the REST API locally or via our ‘CloudFX’ connection from a secure 
cloud endpoint.

If you have a read over the following page it outlines what AutomationFX can do:

https://github.com/unifiedfx/awesome-automationfx

Kind Regards

Stephen Welsh
CTO
UnifiedFX

Sent from my iPad

On 6 Sep 2017, at 17:13, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:


The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

___
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] OT: Add move change

[Lelio Fulgenzi]

The question I have surrounding this is do you swap mac addresses or do you do 
a super copy then delete old one?

There are many apps out there, both Cisco and third party, that are tied to the 
MAC address of the user’s phone.

We’ve seen swapping MAC addresses out is simple and makes sense for most Cisco 
apps, but for those third party apps that synchronize databases via AXL, it can 
cause havoc.

I’m leaning towards updating our MAC process to use supercopy and delete old 
phones as required in secondary systems.



---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott 
Voll
Sent: Wednesday, September 06, 2017 11:10 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] OT: Add move change

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group 
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that 
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott

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

[cisco-voip] OT: Add move change

[Scott Voll]

What do other use for add, moves and changes to there environments?

We have a home grown app that is not working well, to notify Telecom group
about changes to the phones, new users, configuration changes, etc.

Does anyone know of any can'd or cloud based software?  Are there any that
interface with Cisco to automate the process via AXL / SOAP?

Just putting my feelers out to see what is available.

Thanks

Scott
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OT: 4000 ISR and service containers...

[Ki Wi]

Have not tried it yet but it looks like you will have to upgrade from
default 4gb ram/4gb flash to 8gb ram/8gb flash.
>From there, purchase a 200gb ssd.

This cost as much as buying a EN140 (NCE) equipped with 200 GB SSD.

I'm keen to know anyone tried it as well.

On Wed, Sep 6, 2017 at 5:26 AM, Lelio Fulgenzi  wrote:

>
> So in my investigation of new platforms for CUE, I came across the service
> container feature of the ISR 4000. Is it as simple as this model having
> spare CPUs available to quickly spin up a KVM based virtual guest in
> seconds/minutes?
>
> It's quite impressive. Anyone using this in the field?
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519-824-4120 Ext 56354
> le...@uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
> ___
> 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