search

ajitd / boghe

Automatically exported from code.google.com/p/boghe
0 stars 0 forks source link

SMS: application/octet-stream not supported #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start two Boghe apps, press Sign In button on the both of them.
2. In the 1st app, in the unnamed field below the contact list, type the 
address of the 2nd app. Click Start Chat button.
3. In the 'Talking with xxx' window, write text in the unnamed field at the 
bottom and press Send Text button.

What is the expected output? What do you see instead?
The same text should appear in the Talking with window of the 2nd app.
Instead, it shows the message 'application/octet-stream not supported as 
content type'

What version of the product are you using? On what operating system?
Boghe_1.0.55.539.zip

Please provide any additional information below.
The behavior is the same regardless of the SMS type selected on Options -> 
Messaging (either plain text or binary).

The traffic between Boghe apps for both modes is attached.

Note. I expected that chat messages would go through the SIP server, without 
session initiation with INVOKE. At least this would make the Boghe app 
compatible with other SIP clients like X-Lite. Now the latter starts ringing 
once a text message from Boghe gets sent.

Original issue reported on code.google.com by victorx...@gmail.com on 3 Jan 2011 at 10:05

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Boghe supports 3 types of messaging.
1. Text SMS: Use SIP MESSAGE request and the content type is "text/plain". This 
kind of message could be sent to any SIP client such as X-Lite.
2. Binary SMS: Use SIP MESSAGE request but the content type is 
"application/vnd.3gpp.sms" and such messages must be sent to an IP-SM GW.
3. Chat: Use MSRP protocol. The session is setup using SIP INVITE and the 
messages are transported using MSRP messages.

The session window will always initial a chat session (type 3).
To send an SMS (type 1 or 2):
- From a contact or history entry, make a right click and select "send sms".
- From the contact screen at the bottom right click on the forth button to open 
the context menu and select "send sms". Pressing (without using the context 
menu) on the fourth button will always start a chat session (type 3).

This said, I will analyze your trace to figure out why you have such error.

All this will be fully documented in the coming days ;)

Original comment by boss...@yahoo.fr on 4 Jan 2011 at 2:36

GoogleCodeExporter commented 9 years ago 
Fixed in 1.0.56.542

Original comment by boss...@yahoo.fr on 11 Jan 2011 at 1:47

GoogleCodeExporter commented 9 years ago 
Hi, boss...@yahoo.fr

How to display correct text information in SIP client

Original comment by sundl2...@gmail.com on 22 Feb 2011 at 4:10

GoogleCodeExporter commented 9 years ago 
@sundl2...@gmail.com
Could you please attach the network trace?

Original comment by boss...@yahoo.fr on 22 Feb 2011 at 6:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by sundl2...@gmail.com on 23 Feb 2011 at 1:27

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by sundl2...@gmail.com on 23 Feb 2011 at 1:55

Attachments: