Hi,
o Carsten Bock on 11/22/2011 04:04 PM:
Hi,
short question:
Is there any commit rules for the SEMS-repository? I would
yes:
- it must follow the licensing (see COPYING)
- it should be formatted like the code around
- it must compile
- bugfixes should be applied to both master and stable versions, atm 1.4
- smaller changes/fixes can be committed to master right away, for
bigger changes please create a personal branch and commit there first,
we (Raphael or me) will review and merge to master once discussed/reviewed
a) commit a fix for the issue below
fine, thanks, go ahead
b) i want to look into integrating some sort of update-mechanism in
the CallControl interface of the b2b-User-Agent. I want to modify the
yes, this generally makes sense; I'd add another type of CC command
(SBC_CC_SET_CC_TIMER_ACTION), and run a CC function once it's fired.
prepaid_xmlrpc-call-control plugin, so it can retrieve e.g.
authorization for let's say 60 seconds and then, after 60 seconds,
check again and (maybe) get a new authorization for another 60
seconds. This would allow concurrent prepaid calls for a single user.
it's not yet 100% sure, but possibly there will be a prepaid
implementation be open sourced soon which supports concurrent calls.
Stefan
Thanks,
Carsten
2011/11/10 Stefan Sayer<[email protected]>:
Hi,
o Carsten Bock on 11/10/2011 10:53 PM:
Hi,
i just wondered, if the "s="-line has to have content according to the
standard?
The standard is not really clear about this:
Session Name
s=<session name>
The "s=" field is the session name. There must be one and only one
"s=" field per session description, and it must contain ISO 10646
characters (but see also the `charset' attribute below).
(Page 9 of RFC2327)
I've noticed, that my AVM FritzBox will tear the call down, if the
s=line is empty (other devices seem to accept that).
After putting a simple string "call" into the s-line, everything works
fine (changed the SDPFilter.cpp of the SBC-module)
Can anyone confirm, if the s-line must have content to the standard?
yes, it is needed.
have a look at the more current
http://tools.ietf.org/html/rfc4566#section-5.3
or
http://tools.ietf.org/html/rfc4566#section-9
Stefan
Kind regards,
Carsten
--
tel:+491621366449
sip:[email protected]
mailto/xmpp:[email protected]
--
tel:+491621366449
sip:[email protected]
mailto/xmpp:[email protected]
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
