24 Jul
2008
24 Jul
'08
8:41 a.m.
Hi Daniel,
thanks for reply me email. When I use eyebeam Content type is html but with Pidgin it is
as follows:
" application/im-iscomposing+xml" (before sending the IM), and the log in
Openser is.
xmpp: invalid content-type 0x300ff
And Content-Type: text/plain which log in OpenSER is.
xmpp: unable to write to command pipe: Bad file descriptor
So, same result even when content-type is plain text. Like I said, if I run openser as a
single process IM works in both directions. I forgot to say that the version of openser I
use is 1.2.3.
By the way,does the xmpp module support presence or is it just meant for IM?
Cheers,
Cesar
-----Ursprüngliche Nachricht-----
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Gesendet: Donnerstag, 24. Juli 2008 12:44
An: Cesar Troncoso
Cc: users(a)lists.openser.org
Betreff: Re: [OpenSER-Users] XMPP/SIP-SIMPLE Problem
Hello,
On 07/24/08 12:33, Cesar Troncoso wrote:
Hi everyone,
I have a problem with xmpp module. Messages going from xmpp to
sip-simple work fine. The problem I have is in the opposite direction
(from sip-sipmle to xmpp). If I set fork=no or children=1 in my
config file then all messages are sent and received in both directions.
This is what I see in the logs:
xmpp: invalid content-type 0x300ff
xmpp: unable to write to command pipe: Bad file descriptor
Any Idea how to overcome this situation?
what is the content type of the SIP message? XMPP gateway accepts only
plain text messages for now. If it is html cannot be transalted for now
as it requires some processing before converting in a XML stream
required by XMPP.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com