replying to websms generated sms not always working

[GoogleCodeExporter]

What steps will reproduce the problem?

1a. Send sms with caller-id via websms/sipdroid.de
1b. Send sms with caller-id via websms/cherry-sms.com
2. Reply to sms with a sonyerisson k700i

What is the expected output? What do you see instead?

sms-reply should be delivered to the sender (callerid).
instead an error is produced by sonyerisson "unbekannter
empfänger" (unknown recipient).

Please provide any additional information below.

according to other websources, the same error
"unbekannter empfänger" (unknown recipient) is generated if
the sms-flag "antwort anfordern" (request reply) is
set, because this will cause some replying phones to try to
use the senders sms-central-number.

Original issue reported on code.google.com by Roderich...@gmail.com on 2 Jan 2010 at 9:38

[GoogleCodeExporter]

Original comment by felix.bechstein on 2 Jan 2010 at 12:21

• Added labels: Component-Logic, Priority-Critical, Product-WebSMS
• Removed labels: Priority-Medium

[GoogleCodeExporter]

sender-id  has a zerozero prefix ("0049") not the usual plus (+49..), maybe
that's causing trouble?

Original comment by Roderich...@gmail.com on 2 Jan 2010 at 4:25

[GoogleCodeExporter]

0049 should be no problem. i'll play around with the "antwort anfordern" 
(request
reply) flag as soon as there is some time.

Original comment by felix.bechstein on 4 Jan 2010 at 7:52

• Changed state: Accepted

[GoogleCodeExporter]

@cherry-sms: there is no flag to alter :(
@sipgate: mirko should just have a closer look

for android phones there should be no problem to answer these kind of messages.
but i just have no other phone to test with. :(

Original comment by felix.bechstein on 5 Jan 2010 at 5:14

[GoogleCodeExporter]

I will look at the api description of sipgate, but I dont think I can change 
the 
prefix, becouse it is set in the web-admin-page and not set throgh the api-call 
request.

Original comment by mirko.we...@gmail.com on 10 Jan 2010 at 10:44

[GoogleCodeExporter]

well. i'll close that issue due to timeout.
i just don't know what to change to get the reply working with that kind of old 
phones.

maybe you should try an other connector.

Original comment by felix.bechstein on 13 Feb 2010 at 4:08

• Changed state: WontFix