[sr-dev] [kamailio/kamailio] Bad content-length header value after invoking uac_auth() (Issue #3275)

Ay notifications at github.com
Wed Nov 2 14:03:27 CET 2022


### Description
  We are trying to perform an outbound call through kamailio (5.6). When doing so, we are getting an expected 407 response from the trunk provider. As reponse we try to authenticate. This last invite being sent from kamailio to the trunk provider contains a bad content-length field.

if the content header field value was 1234 in the original invite, the last ones content-header field value is 12341234. So it looks like it's not cleared before its set.


### Troubleshooting
this source we used to troubleshoot:

    xlog("L_WARN", "TRUNKAUTH entered, message: $mbu\n");   AT THIS POINT CONTENT_HEADER = 1234 (just an example)
    if(t_check_status("401|407")) {
    $avp(auser) = "testuser";
    $avp(apass) = "credshere";
    uac_auth();
    xlog("L_WARN", "TRUNKAUTH Auth done, updated message: $mbu\n"); AT THIS POINT CONTENT_HEADER = 12341234
    route(RELAY); 
#### Reproduction
See troubleshooting


### Additional Information

  * **Kamailio Version** - output of `kamailio -v`

```
kamailio 5.6.2 (x86_64/linux)
```

* **Operating System**:

```
kamailio 5.6.2 (x86_64/linux)
```


-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3275
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/issues/3275 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20221102/b7d1fa6c/attachment.htm>


More information about the sr-dev mailing list