Home 10 ALEGIDS configuration does not work

[zanmeipaul]

I am based on https://github.com/sipcapture/homer-docker/blob/main/all-in-one/docker-compose.yml Configure this example and add the X-CID header field in SIP. HEPLIFYSERVER_DBSHEMA=mock HEPLIFYSERVER_DBSHEMA=mock HEPLIFYSERVER_LOKIURL= http://qryn:3100/loki/api/v1/push
HEPLIFYSERVER_ALEGIDS=X-CID
But the correlationId field in clickhouse is empty

[lmangani]

This means the X-CID header is not extracted. Not much we can do without knowing anything.
Note settings are Case Sensitive. The feature seems to be working fine in other setups and wasn't changed recently.

[zanmeipaul]

This means the X-CID header is not extracted. Not much we can do without knowing anything. Note settings are Case Sensitive. The feature seems to be working fine in other setups and wasn't changed recently.

hello, The SIP header field of the data sent to QRYN does not contain the correlation_id field. Is there a difference between storing it in the database and sending it to qryn for decorrelation id extraction?

This is my configuration

`services:
clickhouse-server:
image: clickhouse/clickhouse-server:23.3-alpine
container_name: clickhouse-server
restart: unless-stopped
volumes:
- clickhouse_data:/var/lib/clickhouse
- ./clickhouse/opentelemetry_zipkin.sql:/docker-entrypoint-initdb.d/opentelemetry_zipkin.sql
environment:
CLICKHOUSE_USER: qryn
CLICKHOUSE_PASSWORD: demo
CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT: 1
ports:
- 8123:8123
logging:
options:
max-size: "10m"

qryn:
image: qxip/qryn:3.2.39
container_name: qryn
restart: unless-stopped
pull_policy: if_not_present
depends_on:
- clickhouse-server
environment:
CLICKHOUSE_SERVER: "clickhouse-server"
CLICKHOUSE_AUTH: "qryn:demo"
TZ: Asia/Shanghai
NODE_OPTIONS: --max-old-space-size=4096
ports:
- "3100:3100"

heplify-server:
image: ghcr.io/sipcapture/heplify-server:latest
container_name: heplify
restart: unless-stopped
depends_on:
- clickhouse-server
- qryn
ports:
- "9060:9060/udp"
- "9061:9061/tcp"
environment:
HEPLIFYSERVER_HEPADDR: "0.0.0.0:9060"
HEPLIFYSERVER_HEPTCPADDR: "0.0.0.0:9061"
HEPLIFYSERVER_DBSHEMA: "mock"
HEPLIFYSERVER_DBDRIVER: "mock"
HEPLIFYSERVER_DBADDR: ""
HEPLIFYSERVER_LOKIURL: "http://qryn:3100/loki/api/v1/push"
HEPLIFYSERVER_LOKITIMER: 1
HEPLIFYSERVER_LOKIIPPORTLABELS: true
HEPLIFYSERVER_LOGLVL: "debug" # 减少日志量
HEPLIFYSERVER_LOGALEG: true
HEPLIFYSERVER_LOGSTD: true
HEPLIFYSERVER_DEDUP: false
HEPLIFYSERVER_FORCEALEGID: false
HEPLIFYSERVER_ALEGIDS: X-CID,Call-ID,callid

grafana:
image: grafana/grafana-oss:10.4.3
container_name: grafana
volumes:
- grafana_data:/var/lib/grafana
- ./grafana/provisioning/:/etc/grafana/provisioning/
- ./grafana/plugins/k8spacket-nodegraphplugin-datasource:/var/lib/grafana/plugins/k8spacket-nodegraphplugin-datasource
- ./grafana/plugins/qxip-flow-panel:/var/lib/grafana/plugins/qxip-flow-panel
environment:
GF_SECURITY_ADMIN_USER: ${ADMIN_USER:-admin}
GF_SECURITY_ADMIN_PASSWORD: ${ADMIN_PASSWORD:-admin}
GF_USERS_ALLOW_SIGN_UP: false
GF_USERS_DEFAULT_THEME: light
GF_EXPLORE_ENABLED: true
GF_ALERTING_ENABLED: false
GF_UNIFIED_ALERTING_ENABLED: true
GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS: qxip-flow-panel
restart: unless-stopped
ports:
- 3000:3000
depends_on:
- clickhouse-server
logging:
options:
max-size: "10m"

volumes:
clickhouse_data:
driver: local
driver_opts:
type: none
o: bind
device: ./clickhouse_data
grafana_data: {}`

[lmangani]

hello, The SIP header field of the data sent to QRYN does not contain the correlation_id field. Is there a difference between storing it in the database and sending it to qryn for decorrelation id extraction?

No there is no difference but the extracted header will be part of the hep headers. Hard to tell without seeing input/output but i think you should start with a simpler setting if you have X-CID and see if that's related. Ultimately skip the envs and map your own heplify-server configuration if/when complexity grows past a few ENVs, particularly for array entries.

• "HEPLIFYSERVER_ALEGIDS=X-CID"

[zanmeipaul]

hello, The SIP header field of the data sent to QRYN does not contain the correlation_id field. Is there a difference between storing it in the database and sending it to qryn for decorrelation id extraction?

No there is no difference but the extracted header will be part of the hep headers. Hard to tell without seeing input/output but i think you should start with a simpler setting if you have X-CID and see if that's related. Ultimately skip the envs and map your own heplify-server configuration if/when complexity grows past a few ENVs, particularly for array entries.

• "HEPLIFYSERVER_ALEGIDS=X-CID"

After being sent to QRYN, QRYN will be written to clickhouse. I can see the X-CID field at clickhouse. My understanding is that there should be a correlation_id header field in the clickhouse Line field message, but I did not see this field. If successful, where will it be displayed in clickhouse?

[lmangani]

If successful you would see it. Follow the suggestion and make sure its extracted. Your issue is the extraction 99%

[zanmeipaul]

If successful you would see it. Follow the suggestion and make sure its extracted. Your issue is the extraction 99%

I have extracted the custom X-CID field as CID from the log, and now I have two questions: 1 Cannot see the correlation_id field 2 in clickhouse The request initiated by B-leg Invite has an X-CID field, but the response message returned does not have a custom X-CID field. Can the ALEGIDS association function recognize this type of request returned by B-leg? From the logs, it seems that this type of CID is not correctly recognized

[lmangani]

The request initiated by B-leg Invite has an X-CID field, but the response message returned does not have a custom X-CID field.

We only extract what's there. Only if you use HOMER and our APIs you get correlaton, if you use ClickHouse directly you have to do it your way. HOMER doesn't know about calls or legs - its a collection of messages in a database and most of the logic is implemented in our readers when it comes to correlation,etc. Not in the data itself.

[zanmeipaul]

The request initiated by B-leg Invite has an X-CID field, but the response message returned does not have a custom X-CID field.

We only extract what's there. Only if you use HOMER and our APIs you get correlaton, if you use ClickHouse directly you have to do it your way. HOMER doesn't know about calls or legs - its a collection of messages in a database and most of the logic is implemented in our readers when it comes to correlation,etc. Not in the data itself.

I am not directly using ClickHouse, I am configuring it through the case provided by your official website. Heplify server writes data to qryn, who then sends it to ClickHouse. View data through the Grafana and call flow plugins provided by you. The current issue is that I cannot see any information about the correlation_id on Grafana