Hello,
I'm looking at getting richer content for the FAQ wiki page:
* http://www.kamailio.org/wiki/tutorials/faq/main
Probably we can get it good enough with a bit of mobilization for one
week. If anyone is having some questions fitting the purpose of the FAQ,
just add them to the page or send via email.
If you don't have the right answer, just leave it as TBA in the wiki,
via email is fine to send just the question.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
Hello,
some bits were left with the old project name OpenSER, not to disturb
too much at that time and see where everything goes.
Other voices expressed same idea in the past, now everything is stable
and development goes smooth, so it is good to make a decision because
openser is too way back and new comers could be confused.
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that
much as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively openser,
openserro and openserrw should become kamailio, kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some people
using it, but a search and replace should do it
- snmpstats mibs - probably it is going to have some impact as well
Eventually we can start doing it gradually, one or two per release, but
is probably better to do all at once, so people will do one upgrade with
next major release.
Another thing is sercmd, it is in conflict for packaging as both ser and
kamailio install it. It means that one cannot install both kamailio and
ser at same time from packages. One option is to install it as kamcmd.
Because these changes affect users and devels, I sent the message to
both mailing lists. Opinions?
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
Hi all,
A bit new to this open source environment so not sure of the etiquette re.
compile errors in master branch.
Looks like pvar.h (line 167) has been changed post 3.3 branch. Struct
pv_elem_t has a member 'spec' that is now a pointer and previously wasn't.
This is causing auth_db to choke on compile.
Should I raise a bug report or is correct thing to do to discuss here
first. When I feel more "at home" would be happy to submit a patch to fix
if that is the more correct road to follow - assuming it is not simply an
issue my end.
Cheers
Shane
--
Imagination NZ Ltd
Level 6
92 Queens Drive
P0 Box 30449
Lower Hutt 5040
New Zealand
Hello,
if we have a SDP content like this one:
v=0
o=alice 2890844526 2890844527 IN IP4 host.example.com
s=
c=IN IP4 session.foo.org
t=0 0
m=audio 49170 RTP/AVP 97
c=IN IP4 stream.bar.org
a=rtpmap:97 iLBC/8000
m=audio 49170 RTP/AVP 97
a=rtpmap:97 iLBC/8000
m=audio 49170 RTP/AVP 97
c=IN IP4 bar.baz.net
a=rtpmap:97 iLBC/8000
When parsing this function three streams are created:
first one will have ip_addr string equal to "stream.bar.org"
second one: "stream.bar.org" <-- Wrong! it is using same as first one,
instead using session default
third one: "bar.baz.net"
Attached patch solves it.
Kind regards,
Vicente.