5 Feb
2008
5 Feb
'08
4:12 a.m.
Hello,
I have checked the simple-xmpp draft, and for html body, the gateway
have to convert the message in xhtml and then send it to xmpp world.
http://tools.ietf.org/html/draft-saintandre-xmpp-simple-10#section-6
It is not that quick to add. Alternative would be to extract the text
from html and sent then to xmpp. I do not know if there is such c
library that can do it on linux/unix.
Cheers,
Daniel
On 02/04/08 18:07, Ali Jawad wrote:
Dear Daniel
Thank you for your help so far. I would like to know if this limits my
capabilites to communicate with my XMPP server, does this mean that I
can not send Arabic IMs and other advanced features of XMPP ?
Thank you.
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro]
Sent: Monday, February 04, 2008 6:02 PM
To: Ali Jawad
Cc: users(a)lists.openser.org
Subject: Re: [OpenSER-Users] XMPP GW Error "invalid content-type
0x100ff"
Hello,
On 02/04/08 17:41, Ali Jawad wrote:
> x-lite client immediately returned "*Error: *Your contact is not
> online." The Openser logs return the following:
>
> Feb 4 17:05:52 [11929] DBG:xmpp:cmd_send_message: cmd_send_message
>
> Feb 4 17:05:52 [11929] DBG:core:parse_headers: flags=ffffffffffffffff
>
> Feb 4 17:05:52 [11929] ERROR:xmpp:cmd_send_message: invalid
> content-type 0x100ff
>
> My Config is below:
>
> http://pastebin.com/m7707753a
>
can you grab the network trace of the SIP MESSAGE?
Cheers,
Daniel
------------------------------------------------------------------------
Here you go
http://pastebin.com/m3a537c57
Thanks for your help.
thanks, eyebeam follows Indication of Message Composition for Instant
Messaging RFC:
http://www.rfc-editor.org/rfc/rfc3994.txt
It is why the first message has content type:
application/im-iscomposing+xml
The second is the message in the text/html format.
To be compliant with the RFC, as openser simple-xmpp gateway does not
support rfc3994 so far, you should add in your config:
if(is for xmpp gateway)
{
if($hdr(Content-Type)=="application/im-iscomposing+xml")
{
sl_send_reply("415", "Unsupported Media Type");
exit;
}
}
I will check quickly to see if I can send you a patch to support
text/html content type. Otherwise, 415 should be sent back to any
message that has content type other than text/plain.
Cheers,
Daniel
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro]
Sent: Monday, February 04, 2008 5:30 PM
To: Ali Jawad
Cc: users(a)lists.openser.org
Subject: Re: [OpenSER-Users] XMPP GW Error "invalid content-type
0x100ff"
Hello,
On 02/04/08 17:23, Ali Jawad wrote:
> Hi All
>
> I have the following setup
>
> X-Lite Client -> Openser With XMPP GW Module <-> ejabberD on the same
>
> server <- exodus XMPP client
>
> I have enabled presence on the Openser server this allowed me to chat
>
> using the Openser server. The next step was
to use the XMPP GW module
>
> to enable XMPP features using an ejabberd
server. I changed the
> configuration as shown below and logged in using test2 on the exodus
> XMPP client.
>
> I added test2 to the x-lite client and chose send instant message,
>
the
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users