cannot clone xavi from non existing parsed_pv_headers

Mathias Schneuwly via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <[email protected]>
Hi

I'm getting the error "Jul 15 15:15:54 ttel /usr/sbin/kamailio[812316]: ERROR: {1 382 BYE [email protected]} pv_headers [pvh_xavp.c:485]: pvh_clone_branch_xavi(): cannot clone xavi from non existing parsed_pv_headers" on BYE messages. Interestingly, only on the first attempt to read the from user.

I have the following snippet in my `ksr_branch_manage`
KSR.log('notice', f'ksr_branch_manage: 1')
KSR.log('notice', f'ksr_branch_manage: 2: {KSR.pv.get('$x_fU')}')
KSR.log('notice', f'ksr_branch_manage: 3: {KSR.pv.get('$x_fU')}')

The result in the log is
Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE [email protected]} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 1
Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: ERROR: {1 402 BYE [email protected]} pv_headers [pvh_xavp.c:485]: pvh_clone_branch_xavi(): cannot clone xavi from non existing parsed_pv_headers
Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE [email protected]} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 2: 200102
Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE [email protected]} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 3: 200102

Even if there is an ERROR, it seems to be able to read the from user from pv_headers. Is this error just informative and uses the wrong severity, or what does it mean?

I have no modparam for pv_headers. It uses the default configuration and I'm on 5.8.6. 

Regards
Mathias
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.