Closed GoogleCodeExporter closed 9 years ago
This could get complex on the phone. Does your company SIP server require more
than one prefix? 9+ for some calls, something else for international or other
special calls? Can your company SIP server handle E.164 numbers (1 xx xxx
xxxx)? If so, the leading '+' could trigger rules in the SIP server. You could
use the "Contacts Clean Up" app to convert all of your phone numbers to E.164.
This format is OK with mobile providers as far as I know (at least in the US it
is fine). Since this format can't be dialed by ordinary phones (on ATA) it will
only come from SIP phones. The SIP server rules can take care of the
variations.
This is how I have things set up on our company SIP server here (a 3CX PABX).
Original comment by dc3de...@gmail.com
on 31 Aug 2010 at 3:04
First of all I guess you're using a version from the android mmarket
Latest devs version include this feature on csipsimple (development version are
available on the download section of this website ). See the wiki to know how
to install the development version.
Then, go into your account (must have been setup first), press the menu button
and then choose "filters".
You'll find here a complete and powerful rewritting/rules engine that you can
use to automatically rewrite phone numbers just in time when you place a call
from the native dialer.
Just try to play with the feature and let me know if things need to be more
explained about the use so I can change the interface or write a piece of
documentation about this new feature (not enough time to write full docs right
now since there is a lot of development is remaining )
Original comment by r3gis...@gmail.com
on 31 Aug 2010 at 4:39
Thanks for quick reply, r3gis.3R.
Well, I have installed development version and created a "re-write" filter to
add prefix 9 for all phone number begin with 0 (external number outside
company). For example, 028888888 has transformed to 9028888888. It worked great.
Unfortunately, when CSipSimple logged call history in the phone, the prefix 9
also included. So, I could not re-dial that number from the call history using
GSM (instead of CSipSimple) because GSM does not need the prefix 9. What I did
was disable the "Call logs integration" feature. This way CSipSimple never
logged to system history, but its own call history. It's okay, not a big
problem. Thanks again.
hi dc3denny,
Thanks for your suggestion. Anyway, I have no idea what E.164 is. I just don't
want to mess up the company SIP server. The "filter" in development version
works well.
Thanks.
Original comment by myvr...@gmail.com
on 31 Aug 2010 at 9:22
Oh yes I didn't though about that. So tricky issue for call logs integration.
I've added an issue to track it (issue 184). Will not be considered as a
priority (all the more it sounds not so easy to do (reverting regular
expression replacement :/...). But, you're right it should be the correct
behavior to log what you tried to call.
(And even better if we could do that for incoming too... would be great to log
exactly what matches the number it would have been if it was a gsm call).
Original comment by r3gis...@gmail.com
on 31 Aug 2010 at 9:38
Any news on that?
Original comment by misterti...@gmail.com
on 19 Nov 2010 at 3:43
About issue 184? no, not yet, many many things with a higher priority for me,
but feel free to contribute the app ;)
About this issue that's already available in filters/rewriting rule interface.
Original comment by r3gis...@gmail.com
on 19 Nov 2010 at 4:05
Original issue reported on code.google.com by
myvr...@gmail.com
on 31 Aug 2010 at 2:26