This PR allows kamailio to duplicate messages to Homer using HEPv3 [0].
An optional correlation ID (which can contain PVs) can be passed to `sip_trace()`.
The packing macros in hep.h are authored by @camilleoudot and I've just used them.
An example of formats:
```
modparam("siptrace", "duplicate_uri", "sip:127.0.0.1:9062")
...
sip_trace("sip:127.0.0.1:9060", "123"); // duplicate URI + correlation ID
sip_trace("", "345"); // default URI + correlation ID
sip_trace("", "$fU-678"); // default URI + correlation ID with PVs
sip_trace(); // default URI + no correlation ID
```
[0] https://github.com/sipcapture/HEP/blob/master/docs/HEP3_rev12.pdf
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1006
-- Commit Summary --
* sipcapture: add macros to pack HEPv3 chunks
* siptrace: add support for HEPv3
* siptrace: update doc with support for HEPv3
* siptrace: update doc with editor
-- File Changes --
M src/modules/sipcapture/hep.h (47)
M src/modules/siptrace/doc/siptrace.xml (5)
M src/modules/siptrace/doc/siptrace_admin.xml (60)
M src/modules/siptrace/siptrace.c (321)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1006.patchhttps://github.com/kamailio/kamailio/pull/1006.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1006
We have a crash in kamailio 4.4.4 after t_next_contacts() has been called from failure route, if at this very moment when kamailio is preparing new INVITE the caller sends a cancel.
#0 build_res_buf_from_sip_req (code=3186024432, code@entry=487, text=0x25, new_tag=0x7f8dcf5fb2b0 <tm_tag>, msg=0x7f8dbde6cf78,
returned_len=0xb7, bmark=0x4) at msg_translator.c:2395
#1 0x00007f8dcf35f7b2 in _reply (trans=0x7f8dbde70960, p_msg=0x7f8dbde6cf78, code=487, text=<optimized out>, lock=1) at t_reply.c:712
#2 0x00007f8dcf3b5e8b in e2e_cancel (cancel_msg=0x7f8dbde6dff0, cancel_msg@entry=0x7f8dd26bb750, t_cancel=0x25,
t_invite=0x7f8dbde70960) at t_fwd.c:1278
So the scheme is the following: proxy > INVITE < 486 > INVITE* < CANCEL
Victor has investigated this and found that the issue seems to be related to the reply lumps added by append_to_reply when processing initial invite. In order to reproduce this you need children>=2.
When first target replies 486 the proxy calls t_next_contacts() and starts preparing invite to the next target and at this time another process receives cancel and destroys the transaction, the process handling that invite message(*) gets crashed.
While we are investigating the possibility to move the append_to_reply calls to the branch route, would it be possible to avoid crash by some kind of lock mechanism? The thing is that it's not always possible to move append_to_reply to the branch route, e.g. our proxy is deployed behind stateless lb with multiple interfaces and proxy needs to tell lb which interface to use already in the 100 Trying reply it sends to lb as a first thing when receiving a message.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/872
I've detected that the allocated shared memory is always growing due to
```
proxy[2527]: NOTICE: fm_status: count=376594 size= 103410648 bytes from usrloc: ucontact.c: new_ucontact(98)
proxy[2527]: NOTICE: fm_status: count=1882939 size= 110079752 bytes from usrloc: ../../ut.h: shm_str_dup(723)
```
we do have usrloc in db_mode 3 ( DB_ONLY ).
This is kamailio 4.4.4 version
Investigation underway.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/997
### Description
Dokumentation says:
```
If specified and if value of the avp value is not 0, rtpproxy_manage function adds ICE relay candidate attributes to sdp stream(s) containing ICE candidate attributes.
```
I would read it as, if the avp is set and the value is 0 no ICE relay candidate attributes, would be added. Instead a
### Troubleshooting
#### Reproduction
#### Debugging Data
#### Log Messages
```
Feb 20 15:21:45 <local0.err> voip-integration-cust1 kamailio[33439]: ERROR: rtpproxy [rtpproxy.c:2332]: force_rtp_proxy(): invalid ice candidate priority value 0
Feb 20 15:21:51 <local0.err> voip-integration-cust1 kamailio[33439]: ERROR: rtpproxy [rtpproxy.c:2332]: force_rtp_proxy(): invalid ice candidate priority value 0
```
#### SIP Traffic
### Possible Solutions
Accept 0 as a possible value or change documentation to give information that 0 is no valid input.
### Additional Information
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1003