[cisco-voip] social miner setup design queries

[Anthony Holloway]

1) socialminer needs to be accessible by the user.  So, public DNS and
public HTTPS cert.

2) You should have deployed social miner with a public domain to start
with, in the DMZ.  This will make everything easier and cleaner to deal
with.

On Wed, Jan 29, 2020 at 12:24 AM naresh rathore <nareh84 at hotmail.com> wrote:

> hi all,
>
>
>
> i am currently testing web chat in my office server but soon i have to
> deploy it at customer end. i have some queries regarding design.
>
>
>    1. only web server (with build in uccx chat webform) needs to
>    communicate with social miner or the customer who is using website also
>    should be able to reach/access (http/https) social miner directly?
>    2. if customer need access to social miner beside web server, then in
>    that case if social miner hostname is csm.acme.local then internal dns
>    should resolve csm.acme.local to private IP of csm.ame.local but there
>    should be external resolvable name as well for e.g csm.acme.com and
>    should point to social miner. also url in the webchat html file should be
>    changed to csm.acme.com?
>
>
> Thanks
>
> Naray
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200129/065e8581/attachment.htm>