Closed GoogleCodeExporter closed 9 years ago
Really nice idea.
I've already though about the sliding idea (the values was just the simplest
way for
now). But your idea to differentiate from wifi/3g is really very interesting.
It's a
good idea to differentiate wide band codecs.
There is some step to perform before this user interface implementation (like
dynamically get available codecs from the native stack -- hardcoded for now),
but
taken into account, will be done as soon as possible.
Thanks you for the suggestion
Original comment by r3gis...@gmail.com
on 28 May 2010 at 9:07
The slider in the most recent release seems to work well, would like to see
enable/disable (checkmark) next to each.
Original comment by robert.c...@gmail.com
on 9 Jul 2010 at 12:05
I would prefer check boxes too. That way the phone could force a codec
selection. E.g. we allow gsm, g729 and alaw on our asterisk server for that
phone extension. Alaw is at the top of the phone selection but gsm gets
selected each time as codec.
Original comment by dcitele...@gmail.com
on 12 Sep 2010 at 3:26
Well you can already disable a codec.
Just try to long clic on a codec row :)
But I conceed a checkbox is a more user-friendly interface than the long clic
(even if it's widely use in android to get contextual menu on a row).
Original comment by r3gis...@gmail.com
on 12 Sep 2010 at 3:50
I did not know about the ability to disable codecs. That works for me. Thanks.
With that capability (properly documented) there is no need for check boxes
(IMHO). It's only more user friendly because it's obvious and there is no need
to explain the feature. Wouldn't check boxes make the slider obsolete?
Original comment by dcitele...@gmail.com
on 13 Sep 2010 at 5:59
Would it be possible to customize codec priority in an account by account
basis? For example, I connect to the IPPBX at work via WiFi and I use alaw, but
I use g729 to connect to an Asterisk box in the Internet.
Original comment by mau...@gmail.com
on 9 Dec 2010 at 8:16
Issue 65 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 12 Dec 2010 at 7:17
Original comment by r3gis...@gmail.com
on 12 Dec 2010 at 7:18
Well revision 590 provide this feature.
That's really basic approach but should fit needs of almost anybody :
* There is two "profiles" : wide band and narrow band. By default wide band is for networks wifi and others and narrow for 3g, gprs and edge. (Association profile/network type is configurable in expert mode).
I don't think that a more complicated approach is needed. I always try to make
things as simple as possible for users. Here I introduce a complexity but I
hope that users will understand this new approach since not complicated.
@mau... : If you activate a codec not supported by your remote party it will
just be ignored ;). So in your case, (if you have rights to use g729 of course)
just put g729 in the top of the list so that it will be ignored by your ip PBX.
Also new change is that now, pjsip is configured to prefer its own codec
priorities even for incoming calls. (Previously if was an incoming call the
priority taken into account was the one of the remote party).
Original comment by r3gis...@gmail.com
on 23 Jan 2011 at 9:35
now I understand the difference between narrowband and wideband codecs in
csipsimple, thanks
perhaps you should add this description in the wiki, it's very useful.
anyway I'm not able to find the option to associate an account to the network
type, please can you give me a hint? thanks
Original comment by sgn...@gmail.com
on 26 May 2011 at 8:23
As for account per network type it should be done through a plugin. That would
be the clean and extensible way to do things.
Having that inside csipsimple will :
* be not extensible to the infinity of variation this kind of feature mean
* complexify the application for those who does not need the feature.
Original comment by r3gis...@gmail.com
on 29 May 2011 at 11:42
Oh, and this plugin is planned for very soon. Since I now need it for my daily
use, I'll do something ;).
Thanks Alcatel-Lucent for that ;)
Original comment by r3gis...@gmail.com
on 29 May 2011 at 11:43
Original issue reported on code.google.com by
kro...@gmail.com
on 28 May 2010 at 1:44