Before DMQ there were other ways to do similar things. Is DMQ now
considered the best way? Assuming I am using recent stable?
Are there any good guides on clustering Kamailio? I am not finding a
lot of good info on that subject. Specifically, for multi datacenter
active active where things like floating IP's and keepalived are not
really an option.
Hello Community
i'm trying to build kamailio on top of oracle D.B so is there any way to configure kamailio to deal with Oracle D.B and call functions from it ?
Thanks in advance.
Regards
Eyas
Hi,
I'm trying to implement parallel call forking scenario.
Since target clients have different media profiles, I need to set different
rtpengine options for those forked calls.
So according to the rtpengine module documentation, I set via-branch option
on request and response, '1' and '2' respectively ('auto' option is not
working. There is no code implementing this parameter).
However all forked branches have the same via branch id which is the
incoming INVITE's via branch id.
As a result, rtpengine thinks that all the offers belong to the same
session I guess.
It seems I have only 'extra' option with extra_pv_id variable.
In order to use it, I need an elegant way to differentiate forked branches
in request and response processing.
I would appreciate any suggestion.
Hello,
Fosdem 2019 is approaching, so I am writing to see if any of you plans
to go to the event. If there is interest, we can try to organize again a
dinner on Saturday evening, a tradition for our project at the past 10
editions or even more.
Henning Westerholt will give a presentation about Kamailio in the RTC
Devroom, I will be around as well. I know few more developers that plan
to go to the event, so let's see who else from the community wants to
join us. As usual, at Fosdem will be developers from other VoIP
projects, like Asterisk, Janus, CGRates, Homer, Jitsi, ...
At the past editions we typically had two "kamailio" events:
1) an "ad-hoc" developers meeting in the cantina (or other available
room around) to discuss about short term plans for Kamailio -- time and
place being decided as we meet there between us (expected in the
afternoon of Saturday or during Sunday).
2) a dinner at a place nearby, with other VoIP folks joining us
Reply if you plan to go to Fosdem and say if you want to join for a
dinner. Just be aware that you have to pay for your food and drinks at
the dinner, unless we are going to be surprised again by a generous
sponsor that covers partially or completely to dinner.
If you need more details about Fosdem, the website is:
- https://fosdem.org
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com
Hey all,
I need some more clarification on dispatcher alg 8:
“8” - use first destination (good for failover).
What is meant by "first destination"? How is that defined if I have more
than one carrier.
More specifically in our case for some PSTN locations we have this setup:
primary carrier - 1 sip trunk
backup carrier - 4 sip trunks
or
primary carrier - 4 sip trunks
backup carrier - 1 sip trunk
the one that have 4 sip trunks is it going to round-robin through it?
this is setup on our old 4.1.5 release.
thanks
--
Andy Chen
achen@ <achen(a)thinkingphones.com>fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
Hi all.
I want to use SIP early media to play music to the caller in kamailio
IMS installation like this:
http://www.sharetechnote.com/html/IMS_SIP_EarlyMedia.html
I looked a little bit but didn't find ready solution. The information is
vague on this topic.
Should this be done through a module or application server ?
May I need to handle ringing in onreply_route and send OK with SDP to
the caller in SCSCF ?
Regards.
Is it possible to route to the back-end SIP servers via DNS SRV record rather than specifying multiple IP addresses in the dispatcher list on the Kamailio server?
Running in AWS and looking to be able to dynamically update my list of available sip servers if a server goes offline or if a server comes online. Have Cloudwatch/Lambda setup to manipulate the SRV record with the IP address additions or subtractions but when I try to put the SRV record as the destination in dispatcher, it fails.
Hello,
Kamailio SIP Server v5.1.7 stable release is out.
This is a maintenance release of the previous stable branch, 5.1, that
includes fixes since the release of v5.1.6. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.1.x. Deployments running previous v5.1.x
versions are strongly recommended to be upgraded to v5.1.7 or to v5.2.x
series.
For more details about version 5.1.7 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2019/01/kamailio-v5-1-7-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Note: the branch 5.1 is the previous stable branch. The latest stable
branch is 5.2, at this time with v5.2.1 being released out of it.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com
Hello,
I am considering to release Kamailio v5.1.7 later this week, likely on
Thursday, January 31, 2019.
As usual, here come the notice to report any issue that you are aware of
and not yet registered on the bug tracker in order to give them a chance
to be analyzed and eventually fixed before the release. Also, take a
look at the branch 5.1 in git and check if there are any missing commits
from those you expected to be backported.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com
