Guys,
any comment? Ideally going spark is the best but the lack of voice
gateways/ direct sip trunk support seems to force us back to hybrid model?
Regards,
Ki Wi
On Mon, Jun 6, 2016 at 3:49 PM, Ki Wi wrote:
> Hi James,
> you are right regarding the phone registration on
Hi James,
you are right regarding the phone registration on Spark directly. However,
for the voice gateway connectivity for voice countries, looks like we will
have to go via Hybrid method. :(
If that's the case + customer have MPLS today. I will prefer to have the
voice traffic over MPLS. At
Hello,
I don't believe that's the case. According to Cisco, you register the
phones directly to Spark. Check out
http://www.cisco.com/c/en/us/solutions/collateral/unified-communications/hosted-collaboration-solution-hcs/datasheet-c78-736823.html#_Toc444123188
.
This could eliminate the need for
Hi James,
It definitely make more sense. However, if this is to go to spark, I will
need similar equipment upfront as well.
First create a UCM cluster.
Establish hybrid spark connectivity (this requires additional expressway C
instance for host connector stuff on top of expressway C pair)
Since
Hello,
I wonder if a cloud-based solution such as Spark wouldn't make more sense
than implementing an on-premise system.
James
On Mon, Jun 6, 2016 at 2:14 AM, Ki Wi wrote:
> Hi Group,
> I have this customer requirement where they have 3 locations (Singapore,
> US and UK)
Hi Group,
I have this customer requirement where they have 3 locations (Singapore, US
and UK) . Majority of their users will be on the move (around the world).
Users have to connect to the phone system via Internet.
The intention is to have the UCM cluster in Singapore and have the
expressway C/E