-
Notifications
You must be signed in to change notification settings - Fork 264
Examples: SONUS Logs
The Sonus SBC does not (yet) provide dynamic means for always-on packet monitoring except switch-based port mirroring/spanning. The only available resource to fetch information from is weblog.log which can be to some extend parsed and recycled using paStash
This guide is a user-provided, experimental workaround and should not be used as reliable HEP source.
The first step is to install paStash on our middleware HOST
# git clone https://github.com/sipcapture.pastash
# cd pastash
# sudo npm install
Configuration involves three stages: input, filter, output
Adjust the following parameters as needed:
- input > file > path
- output > hep > host, port
Save the config file locally, ie: /opt/pastash/sonus.json
input {
file {
path => "/var/log/sonus/webui.log"
# When testing with a static file:
# start_index => 0
}
}
filter {
multiline {
start_line_regex => /^\[\d{4}-\d{2}-\d{2}/
}
grok {
match => '(?m)\[%{TIMESTAMP_ISO8601:timestamp}\] %{WORD:pid} %{WORD:seq} \n%{GREEDYDATA:payload}'
}
regex {
regex => /From:.*\@(.*)\:(\d+)/
fields => [srcIp,srcPort]
}
regex {
regex => /To:.*\@(.*)\:(\d+)/
fields => [dstIp,dstPort]
}
regex {
regex => /Call-I.*: (.*)/
fields => [correlation_id]
}
}
output {
if [tags] != "_grokparsefailure" {
hep {
host => '127.0.0.1'
port => 9063
hep_id => 2222
hep_type => 1
}
}
}
It's time to run our recipe and check for results:
./bin/pastash --config_file=/opt/pastash/sonus.json
If everything is configured correctly and wind is on our side, paStash should convert logs to HEP-SIP.
- Fragmented messages are not yet handled
- IP/PORT extracted from signaling, unreliable source
- no caching from loglines preceding the SIP methods
- only tested by a few users, needs feedback & tuning
(C) 2008-2023 QXIP BV

HEP/EEP Agent Examples:
- CaptAgent
- HEPlify
- Kamailio
- OpenSIPS
- FreeSwitch
- Asterisk
- sipgrep
- sngrep
- RTPEngine
- RTPProxy
- Oracle ACME SBC
- Sonus SBC
- Avaya SM
- Sansay SBC
HEP/EEP Agent Examples (LOGS):
HEP/EEP Proxy:
Extra Examples:
- Custom JSON Stats
- RTCP-XR Stats
- GEO IP Maps
- Janus/Meetecho-WebRTC
- Cloudshark Export
- Encrypted HEP Tunneling
- SNMP Monitoring
- FreeSWITCH ESL Monitoring
- Kazoo Monitoring
- Speech-to-Text-to-HEP
Extra Resources:
