This is purely a guess, but I think the fact that we don't use a lot of the
features available in ESXI is why Cisco doesn't have us reserve 8gb. I've
never had an issue with running out of ram on a production system, always
cores.
On Fri, Oct 30, 2015 at 8:58 PM, Anthony Holloway <
avholloway+cis
Hey All,
I'm trying to understand the concept of ESXi's RAM requirements, and with
5.5 VMWare says the minimum is 4GB, but they do recommend 8GB for "full
features."
When I look at this one guide as an example:
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#BE6000H.C2.A0Server
; --
>
> Message: 11
> Date: Thu, 29 Oct 2015 17:41:55 -0500
> From: Charles Goldsmith
> To: Scott Voll
> Cc: "cisco-voip@puck.nether.net"
> Subject: Re: [cisco-voip] Remote Phone Control -- Opinions
> Message-ID:
&
Nice list. Thanks for the feed back.
Scott
On Fri, Oct 30, 2015 at 9:22 AM, Tom Sparks
wrote:
> I recently did some research into these tools and here are my pros and
> cons for whoever is insterested.
>
> *UnifiedFX, Singlewire*
> Pros: nice, functional, affordable
> Cons: thick client, po
Caller ID will normally survive call-forwarding, unless you are rewriting it
somewhere. In which case, the solution is to not do that, as Matthew explained.
There's a good chance you are already sending the correct caller ID (check out
the debug isdn q931 on your gateway to confirm). But since y
I recently did some research into these tools and here are my pros and cons
for whoever is insterested.
*UnifiedFX, Singlewire*
Pros: nice, functional, affordable
Cons: thick client, point tool so not great for making available to a team
of users
*Variphy*
Pros: decent, server-based, does othe
I add to the UnifiedFX solution for remote phone control. We still are a
strong Singlewire shop with their InformaCast product for notification, both
informational and emergency. With the drop in support of the RemotePhone
software it was very nice to find the UnifiedFX solution. Very happy
Hi,
I heard there are Cisco phones with built-in echo service, do you know any
by chance?
Thanks,
Amanda @ Sevana
http://sevana.biz
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
It depends on where you are programming the outbound Caller ID. The redirecting
CSS is the path used to get to the mobile so as long as nothing in that path
sets the ID it will pass through.
We use to program the CID directly on the MGCP PRI configs in CUCM. With
mobility we moved it to the rout
In Call Manager ver 10.5, is there any way when a call comes in through a PRI
(outside of the network) to a DID and then forwards to a Remote Destination
configuration to pass the caller ID along instead of the default number
associated with the PRI?
_
10 matches
Mail list logo