Closed GoogleCodeExporter closed 9 years ago
I think the SIP provider should accept '+' ;-)
Like that it can choose the best route for his server and services.
Original comment by samuelv0...@gmail.com
on 4 Jan 2009 at 10:05
I had the same problem and starting to strip off the "+" in all my address book
entries (lots). If this can be fixed easily that would be great. The option
just
to ignore the "+" would probably also work.
Original comment by quinlanr...@gmail.com
on 4 Jan 2009 at 10:06
My SIP provider does not accept a '+' in front of numbers, so it would be good
to
have siphone translate it into 00 before sending. That would be great, since
for
different reasons I don't want to remove the '+' in all my address book entries.
Original comment by psperi...@sunrise.ch
on 5 Jan 2009 at 11:48
Original comment by samuelv0...@gmail.com
on 6 Jan 2009 at 9:50
The problem is that some ITSPs don't adhere to E.123, this means that they do
not recognize the '+' character
as the trigger for the carrier to process as an international call.
You can save alot of headaches by creating an option for E.123 Masking, if
activated, the options would be -
"Ignore", "Change to 00", Change to "011". European ITSPs would process 00 as
the international access code
and 011 is the code for US ITSPs. When an outbound call is processed, it would
basically do a simple search-
and-replace for the + character, either deleting it or modifying it.
Original comment by avery.gl...@gmail.com
on 9 Jan 2009 at 3:23
Avery your are right, and I stopped this development for the moment.
Because Siphon can't correct all misconfiguration at all providers ;-)
When I decided to correct this, users could define the access code for '+'.
Original comment by samuelv0...@gmail.com
on 9 Jan 2009 at 8:04
Unfortunately my VoIP provider doesn't recognize the + character either.
I'd rather not replace the + with something else in my address book, as it would
break when I take my iPhone abroad and do want to keep my address book
functional for
regular GSM/3G calls.
Having an option to do the replacement, where we can choose what to replace it
with
(e.g. 011 for USA, or 0011 for Australia) would be really desirable.
When I use Fring, it pops up a dialogue box where you can edit the number before
dialing---so I can, rather inconveniently, edit the number and do the
replacement myself.
Thanks!
Original comment by jpa...@gmail.com
on 22 Jan 2009 at 12:56
This the resolution of this issue depends of your provider.
Maybe if your sip providers don't support '+' because they don't accept
international
call.
List of international prefixes:
http://en.wikipedia.org/wiki/List_of_international_call_prefixes
Original comment by samuelv0...@gmail.com
on 22 Jan 2009 at 8:56
Hello Samuel!
Imho the best solution would be to have a translation mask.
In my case its even more complicated then + -> 00:
I have my own VoIP PBX running and i need to dial 0 to get a free line.
So my translation would be +# -> 000# or 00# -> 000#
I think you get an idea ;)
P.S. Thanks a lot for your eford and great work, i discovered your app
recently!!!!
Original comment by tom_...@yahoo.com
on 22 Jan 2009 at 2:05
Hi Samuel,
My ITSP supports international dialing, but doesn't recognize the + character.
I've tried contacting them so that they fix up their service, and substitute +
for
0011 (Australia), but they're not very accommodating.
The only solution then, is for me to add 0011 to all of my address book
entries. But
I now reside in the US, where + is 011, and that then screws up my iPhone
address
book. It becomes even more complicated when I'm traveling abroad on global
roaming...
The resolution for me is then to change ITSPs, or use another SIP client. :(
Siphon
is a really nice, clean client; a real shame if the latter becomes the only
option.
Original comment by jpa...@gmail.com
on 22 Jan 2009 at 8:54
version 2.0.3
Original comment by samuelv0...@gmail.com
on 1 Feb 2009 at 5:01
Issue 166 has been merged into this issue.
Original comment by samuelv0...@gmail.com
on 6 Mar 2009 at 12:14
Original issue reported on code.google.com by
aleksand...@gmail.com
on 4 Jan 2009 at 9:51