Could not POST metadata to HTCC

[cavagnaro]

[quote author=juagarod link=topic=10454.msg47603#msg47603 date=1499595382]
Thanks Kubig,

I centered my attention into the Elastic Search configuration. The ES deployment seemed to have no issues at all (it was a stand-alone deploy), so finally I made some tweaks following the doc for the application.yaml Elastic Search part and voilá:

2017-07-09 04:36:31,171 http_client DEBUG Cookie header added
2017-07-09 04:36:33,078 metadata_client DEBUG POST: [url=http://10.100.47.75:8080/internal-api/contact-centers/78d61955-1eb9-4957-918d-8451461d7250/recordings]http://10.100.47.75:8080/internal-api/contact-centers/78d61955-1eb9-4957-918d-8451461d7250/recordings[/url]: Response Status: 200
2017-07-09 04:36:33,094 process_metadata DEBUG Wait for call to end: 10
2017-07-09 04:36:38,141 config_server DEBUG no more events from config server
2017-07-09 04:36:43,109 process_metadata DEBUG Wait for call to end: 10
2017-07-09 04:36:53,125 process_metadata DEBUG Wait for call to end: 10
2017-07-09 04:37:03,141 process_metadata DEBUG Wait for call to end: 10
2017-07-09 04:37:13,157 process_metadata DEBUG processing record: FRFQ23B0AD5KF6RPTDRG95IKI0008N2L
2017-07-09 04:37:13,173 metadatarecord DEBUG Found matched username for recordDN: mzambrano
2017-07-09 04:37:13,173 process_metadata DEBUG Sending to SM: FRFQ23B0AD5KF6RPTDRG95IKI0008N2L
2017-07-09 04:37:15,407 metadata_client DEBUG POST: [url=http://10.100.47.72/interactionreceiver/]http://10.100.47.72/interactionreceiver/[/url]: Response Status: 200

We are currently trying to configure a Genesys user to check the recording and finish the cycle, but it gives me an error in authentication in the SM... Is there a catch in configuring Genesys users to enter SM?

Best regards,

Juan
[/quote]


what exactly did you fixed or modified?? I am stuck at same issue and have no clue on what I am missing...

[cavagnaro]

This is my file

[quote]

index.analysis.analyzer.whitespace_lowercase.tokenizer: whitespace
index.analysis.analyzer.whitespace_lowercase.filter: lowercase


index.analysis.analyzer.mediaPartitionAnalyzer.tokenizer: path_hierarchy


threadpool.index.queue_size: -1
threadpool.bulk.queue_size: -1


path.conf: /etc/elasticsearch
path.data: /usr/share/elasticsearch/data


node.name: GGG
cluster.name: GGG_GIR


transport.tcp.port: 9300
http.port: 9200


discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: 172.117.179.171
discovery.zen.minimum_master_nodes: 1


gateway.recover_after_nodes: 1
gateway.recover_after_time: 1m
gateway.expected_nodes: 1
[/quote]

[cavagnaro]

Fixed, my issue was that in HTCC ElasticSearch Settings was using http port 9200 when should have been 9300