Hi Kristian,
thank you. I'll check this. I think in some cases we are using even a higher lifetime.
Could you please send me a patch with your changes for the pua_dialoginfo module in case we run into the same issue.
Toni
On Tuesday 22 October 2013 13:19:01 Kristian Høgh wrote:
>Hi,
>
>I think I've got the same issue.
>At call creation we set dialog lifetime to 6 hours.
>pua_dialoginfo uses that value and send PUBLISH for each hour, even after the dialog terminates.
>After 6 hours the entry is deleted.
>
>To prevent the updates, I've made a small change to pua_dialoginfo module, which set pua-dialog timeout to 300 sec. when the dialog terminates.
>pua_dialoginfo then sends PUBLISH, which updates presence.
>
>Regards,
>Kristian Høgh
>
>
>On Monday 21 October 2013 15:21:16 SIP Guru wrote:
>>/ Hi,
/>>/
/>>/ expired entries in pua table won't be deleted.
/<>/ And kamailio keep sending PUBLISH's for expired entries.
/>>/
/>>/ Am I missing something ?
/>>/
/>>/ Toni
/>>/
/>>/
/>>/
/>>/ _______________________________________________
/>>/ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
/>>/ sr-users at lists.sip-router.org <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
/>>/ http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
/>
Hi,
I am also looking for a 'group pickup' function with Kamailio.
Once I have the information on the call I want to get how would I 'grab' the
call.
My calls are being processed with the tm module.
I imagine I send an INVITE with the 'replaces' header but what Kamailio
module would process that and what would the config look like?
Many thanks
John
> Hello,
>
> this is a custom implementation, only for phones that have programmable
> buttons. It is not really recommended way to do it.
>
> Better rely on standard specs out there and use presence extensions for
> such feature -- in kamailio you would need to use modules such as dialog,
> presence, pua, presence_dialoginfo and pua_dialoginfo.
>
> Cheers,
> Daniel
>
>
> On 5/14/12 1:15 AM, M.C. wrote:
>
> Hi all,
> I want to implement a "group pickup" (asterisk like) with Kamailio and
> Snom phones.
> I found in the changelog this comment:
> "- an useful application - call pickup:
> - INVITE comes in, callee is in a pickup group
> - store callid, cseq, etc in database or notify the other phones in
>
> the group (easy to do for snom phones and extra programmable
> buttons) via uac_req_send()
> - send a remote control command telling which call to pickup
> (callid, cseq) and where to redirect. In config, call
> t_cancel_callid(). in failure route for INVITE catch the cancelled
> transaction (flag is set), get the new destination (e.g., stored
in
> htable) and forward the invite there""
>
> regarding new functions in tmx module, but I have found no examples in
kamailio documentation.
>
> Is this the way to implement a group pickup in kamailio?
Hi all...
I am trying to do file transfer between IMS clients (web-based WebRTC and android RCS native client). The fisrt test scenario is browser-to-browser (WebRTC) using JSSIP stack. The second scenario is RCS-to-Broswer or Browser-to-RCS. My testbed consists of OpenIMS and OverSIP for WebRTC clients and Kamailio MSRP Relay for file transfer
For file transfer I am using the msrp-crocodile library...
The scenario browser-to-browser works so far without problems. But in the second scenario I have the following problems:
* When I try to transfer a file from the RCS client to WebRTC client , kamailio sends the message "error ""481", "Session-does-not-exist", however the file is sent, when I click send for the second time...
* When I try to send a file from WebRTC client to RCS client, WebRTC client sends all file chunks to kamailio, kamailio receives the chunks but it doesn't forward them to the RCS client, in the console I see some errors pointed to the configuration file, however I don't know what exactly the problem is. In the attachment please find the logs and the configuration file of the kamailio msrp relay...
Can any one help me to solve this problem or give me useful hints?
Thanks a lot in advance....
Medo
In the current Kamailio TLS module document, there is a statement about
tls.reload being unsafe. But the only way to periodically update CRL
without restarting Kamailio is to use tls.reload. In our test with
tls.reload for CRL, it seems Kamailio would crash after about 100 times
of tls.reload in 5/6 hours. The core dump indicates memory access
violation, signal 11. We compiled Kamailio with openssl 1.0.0-fips.
Would appreciate some insights on tls.reload and ideas to fix the crash
issue. Thanks,
Having an odd issue with dialog profiles, if I try to set/check profile based on $fU or $rU call is always rejected due to call limit, but $ru or $fu work without an issue.
Example using $fU-
$avp(s:checkuser) = $fU;
set_dlg_profile("quota","$avp(s:checkuser)");
dlg_manage();
get_profile_size("quota","$avp(s:checkuser)","$avp(s:calls)");
avp_db_load("$avp(s:checkuser)/username", "$avp(s:callquota)");
if ($avp(s:calls) <= $avp(s:callquota))
.......
If I change checkuser to $avp(s:checkuser) = $fu; it returns the correct result.
Any explanation for why this is?
[cid:image001.gif@01CECF2B.581704D0]
I'm looking for some information about how best to monitor presence
events within kamailio? Ideally I'd be writing a python application
that will monitor specific endpoints within kamailio and once there
state changes I do my thing.
I know tapping into the database is an option, but figure I see if
there is another method. EG: Opening a websocket to stream events?
--
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger(a)polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger
Hello there,
I am trying to setup a Kamailio (3.3) + Linphone + Jitsi based private calling system (users can call each other but not call out of the network).
Agents can be behind NAT (think Verizon cellphone or home-users behind their router). I started with the default setup and have tried different settings for NAT/rtpproxy. Currently, all my users register onto the Kamailio server. Users who are not behind a NAT (Jitsi on the internet) i.e. with Public IPs are able to successfully make audio/video calls.
I have RTP proxy setup / running as well, and calls to rtpproxy_manage() as required. The process is running and Kamailio is configured to know that the RTPproxy is listening.
I had to switch to using TCP on some of the my UAs because of provider blocking UDP traffic. So they are able to register, yet calls are not completed. The call looks like it connects but no media (audio or video goes through).
I have read a lot of the forums on NAT - and am trying to solve for a couple of big issues:
1. Figuring out when a UA is behind a NAT, and handling the RTPProxying appropriately.
2. while ngrep-ing UDP packets occassionally I see "Warning: 399 sipalg "Unauthorized" or Bad request. based on what I saw on the internet, it has to do with the service provider (Verizon) messing with the packet. Is there a way arount this?
Any help is greatly appreciated!
Thanks
Pranv
Hello,
I installed kamailio 4.0 with packages (apt-get install kamailio).
So everything works well.
Now I want to install carrierroute modules to route some calls.
Please how can I do it?
Help!!!
thanks.
Dzexolokpli AMOUZOU
Hi Kamailio community,
I am working around with Kamailio (V 4.0.3), its XMPP module- component
mode and jabbed2 server, intended to get file transfer feature between two
SIP clients. In a way while surfing through the blogs i got some info like
this:
'In component mode, a sub domain is diverted to respective component,so
you don't need users in XMPP sever'.
(http://lists.sip-router.org/pipermail/sr-users/2010-August/065209.html).
With this my question is: what does it mean ?
Is it mean like i dont need to register xmpp clients to jabbedd2(xmpp)
server ? If this is the case, How can i use my SIP users (registered to
kamailio server) in jabberd2 server context ?
Even XMPP module's man page doesn't give clarity about these questions.
Any help will greatly appreciate.
Regards,
Ravi
