Hi Daniel
As you mentioned the original reason for this module was not IMS but rather
to support some new features, in particular forking. It is not
particularly specific to IMS.
Unfortunately we have not managed to merge with the normal dialog module as
we had originally intended.
I do hope a
Hi,
On 12/10/2015 01:33 PM, Alex Balashov wrote:
> I tested an approach in which all initial rtpengine_manage() calls (in
> support of a new SDP offer) were made in a branch_route[], and this
> appeared to work.
>
> Is this the 'orthodox' way to do it?
That's the way we're using it also.
Andrea
Ok I got it - endpoint must send MESSAGE to sip:conference-n...@domain.name,
but initially it sends to conference-name.
So as I understood - if (is_method("MESSAGE") && !(starts_with("$fU",
"chat"))) should make everything work correct.
Sorry for emotions :)
2015-12-15 19:00 GMT+02:00 Alexandru Co
Hello again
First of all I wanted to ask if someone ever implemented that
http://kamailio.org/docs/modules/4.3.x/modules/imc.html with WebRTC
Second question is - I don't understand the logic. In description is said:
Handles Message method.It detects if the body of the message is a
conference comm
upd: Let me describe my use case. I need conference chats. Clients are
1001-1...@domain.name
Conference is 3...@domain.name
Messages are sent from 1001-1...@domain.name to 3...@domain.name
Every user joins conference room chat-3500. Join is successful - but
nothing more. Messages are not relayed an
Hi,
I would prefer to maintain the dialog and rtp session, however push come to
shove maintaining the RTP session would be sufficient.
Is it possible to do state-full failover of both the dialog and rtp or just
rtp?
Any recommendations on documentation or how-to to read that would point me
in th
Hello Daniel,
Thank you for your help.
Ok pua_usrloc modules seems good for me.
I try to use it :
I add these routing in route[REGISTAR]
if(is_method("REGISTER") && from_uri=="sip:122@192.168.0.186" ) {
xlog("L_INFO", "LBO - pua_set_publish() call for $rm from
$fu (IP:$si:$s
Well, that depends. Is your objective really RTP failover, or also failover of
dialog state (e.g. for some accounting purpose)?
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954
Hi,
Is statefull failover a function of the Kamailio or RTPProxy application?
Would they be able to do the statefull checkpointing between servers, or is
there a third-party tool that can be used?
Regards,
On Mon, Dec 14, 2015 at 12:00 PM, Alex Balashov
wrote:
> On 12/14/2015 11:51 AM, Frank C
Hello,
On 15/12/15 14:16, Loïc Boissy wrote:
> Hello,
>
> I use kamailio 4.3.2 with the presence module.
> When the contact is able to manage its presence, No problem for me.
> But when a contact doesn't manage it presence, i would like to know if
> it is possible to generate a sip message (like a
Hello,
I use kamailio 4.3.2 with the presence module.
When the contact is able to manage its presence, No problem for me.
But when a contact doesn't manage it presence, i would like to know if it
is possible to generate a sip message (like as a simple presence message)
with kamailio?
The goal of
Yes, sometimes there are more than one INVITE (custom platform specific
behavior), in case of 1 INVITE per-dialogue it works nice. Can you suggest
something to cover such cases?
2015-12-15 14:12 GMT+02:00 Daniel-Constantin Mierla :
> Maybe there is a parallel forking and one branch gets timed out
Hello,
I am under the impression that the name dialog_ng creates confusion out
there and some people are using it instead of the classic dialog module.
Although it was started with goals of reworking dialog module with a
different concept (which was discussed mainly by some guys that
afterwards c
Hi Michael,
a way could be to have two different dispatcher sets (one for each mvno).
Then you could store the dispatcher set associated to each user in the
usr_preferences table and use it in the routing script.
Something like this in your routing script:
avp_db_load("fU", "$avp(dispatcher-set)"
The reason for my question is that we are 2 mvno's who wants to share a
single sip mvno trunk - and want to have our individual customers routed
according to who owns them - but also have the dispatcher functionallity
for "load-balancing".
On Tue, Dec 15, 2015 at 1:23 PM, Michael Nielsen
wrote:
Hello everyone,
I know kamailio can be configured into almsot everything for SIP - and that
the dispatcher function is already build for dispatching between multiple
sbc's etc...
Is it possible to use the dispatcher for routing between multiple sbc's
accroding to called subscriber?
So I can make
Mysql is in default Debian distro, install it from there.
So, remove from your apt list:
deb http://repo.mysql.com/apt/debian wheezy mysql-5.6
deb-src http://repo.mysql.com/apt/debian wheezy mysql-5.6
deb http://repo.mysql.com/apt/debian wheezy mysql-apt-config
Then do apt-get update and install
Maybe there is a parallel forking and one branch gets timed out (in this
case 408 is selected against 486). How many INVITE requests do you see
being sent out? Or you can eventually make the sip trace available for
viewing on this mailing list or some web site/pastebin out there.
Cheers,
Daniel
O
I use sngrep to track view the flow and I'm pretty sure it's accurate
enough to tell me that.
Here's relay route:
route[RELAY] {
# enable additional event routes for forwarded requests
# - serial forking, RTP relaying handling, a.s.o.
if (is_method("INVITE|BYE|SUBSCRIBE|UPD
From what you describe, the reply should be going back to the sender. Are you absolutely sure that it's not? If so, are there any other actions you could be taking somewhere to drop it, such as in an onreply_route
Hello everyone!
I need to relay 486/408/... other failure codes back to initial INVITE
server. Here
http://lists.sip-router.org/pipermail/sr-users/2010-November/066382.html is
recommended just to exit failure_route, but that didn't work for me. I need
that to let Freeswitch know which cause has end
Ganesh,
After issuing command $sudo apt-get update, adding the repo we are getting
the below error.
root@debian:/etc/apt/sources.list.d# apt-get install mysql-server-5.6
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'mysql-community-serve
22 matches
Mail list logo
