Hi all,
I am using uac_replace_to to replace the TO header on requests. I
understand it can only be called once per message and the recommendation is
to store the updated value in a pvar and apply it in the branch route.
However in my scenario I wish to first try one endpoint and then if it gets
Hi Richard,
Thanks for the tip, I had indeed overlooked the return value.
Cheers
Matthew
On Tue, 5 Mar 2024 at 05:34, Richard Chan wrote:
> In the method can you put
>
> return 1
>
> at the end. KEMI python is very strict on an int return value.
>
> On Tue, 5 Mar 2024, 07:08 Marrold via
Hello Christoph,
Kamailio is providing a lot of different functions. Some of these functions
could be used to implement a network element with features which are forbidden
in the RFC 3261 and/or other relevant RFCs.
One of the most prominent examples is e.g., rewriting of From and To headers.
Trying to setup Kamailio with MS Teams Direct Routing.
I am familiar with the integration steps required by Microsoft (using contact
header as FQDN, certified CA for certificate) aswell as the famous guide;
https://skalatan.de/en/blog/kamailio-sbc-teams +
The RFCs are correct; strictly speaking, a proxy should not alter the
encapsulated message body, or most other SIP message attributes.
Kamailio is a huge toolbox with many capabilities, not unlike a programming
language. It gives one the power to do a great many things.
Some of these things
Hi all,
it might be a minor issue, or it might not be an issue at all, but I stumbled
over following statements in RFC 3261:
Chapter 16.6 Request Forwarding (of a proxy)
1. Copy request
The proxy starts with a copy of the received request. The copy
MUST initially
Thanks for the help.
I've ended up creating a route invoked by rtimer module where i check all
active dialogs and for each of them sent a radius accounting update.
Cheers,
Duarte
__
Kamailio - Users Mailing List - Non Commercial
