Hello,
I think he was looking in this case for something different. 😄
You will find also with google on kamailio.org some older howto and also images
with kamailio IMS examples, i think. There are also cfg examples in the git
repository (misc/examples or so)
Cheers,
Henning
--
Henning Weste
Hi,
i am using htable to assign internal transaction index and label.however
its unable to assign the index and label
modparam("htable", "htable", "hte=>size=8;autoexpire=300")
$sht(hte=>id_index::$rU) = $T(id_index)
$sht(hte=>id_label::$rU) = $T(id_label);
Logs:-
Hello Luke,
A simple web search on "kamailio ms teams" will lead you to this link:
https://www.kamailio.org/w/2019/10/using-kamailio-as-sbc-for-microsoft-teams/
>From which you can navigate to this link:
https://skalatan.de/en/blog/kamailio-sbc-teams
Regards,
Ovidiu Sas
On Sun, Sep 27, 2020 at 5
Hello,
I'm trying to use xavu as described in Kamailio documentation:
https://www.kamailio.org/wiki/cookbooks/5.4.x/pseudovariables#xavu_id_-_xavus
$xavu(a=>b) = "xyz"; # <- two level naming supported
However, this does not seem to work. The second level is ignored.
When calling pv_xavu_print()
Daniel-Constantin Mierla writes:
> For SIP URI the parameter value is always ws:
>
> Â * https://tools.ietf.org/html/rfc7118#section-5.2
Yes, according to that RFC, but does it make any sense, since how you
tell based on usrloc received value if ws or wss was used for the
registration?
-- Juha
Hi Team,Â
Can somebody share a guide to setup Kamailio IMS in ubuntu or centos, please?Â
ThanksLuke___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
For SIP URI the parameter value is always ws:
 * https://tools.ietf.org/html/rfc7118#section-5.2
Cheers,
Daniel
On 26.09.20 20:12, Juha Heinanen wrote:
> It may be related that also usrloc received uri has ;transport=ws:
>
> sip:192.168.43.83:51176;transport=ws
>
> instead of ;transport=wss.
>
