5 Aug
2008
5 Aug
'08
11:07 a.m.
Hi Daniel,
I updated my test system to OpenSER 1.3.2 and I don't have the problem anymore, IM
works fine in both directions. I think however that it would be good in the future to
support different content types and not only text/plain.
I made some tests with pua_xmpp module and found some "mistakes" in the docu. I
will list them here:
1.server_address of Exported Parameters has to be a valid SIP-Address and not only the IP
of the server: for example
modparam("pua_xmpp", "server_address",
"sip:160.23.23.10:5060")
if not tm module reports some errors.
2. Instead of Notify2Xmpp() in example 1-2, the function should be pua_xmpp_notify(),
otherwise the function is not find by any module:
DBG:core:find_cmd_export_t: <Notify2Xmpp> not found
CRITICAL:core:yyerror: parse error in config file, line xxxx, column 33-34: unknown
command, missing loadmodule?
3.Same example 1-2, I had to add in my config the address of my server for the NOTIFY to
be properly sent out like this:
if( is_method("NOTIFY") && (uri=~"sip: 160.23.23.10:5060" ||
uri=~"sip:.+@sip-xmpp.siphub.ro"))
After those chages presence works fine in both directions except for one error:
ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:<sip:jabberID*xmpp.openser.org@sip-xmpp.siphub.ro >
And that's all, I will continue testing these modules. If I find other issues I will
let you know.
Cheers,
Cesar
-----Ursprüngliche Nachricht-----
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Gesendet: Donnerstag, 24. Juli 2008 14:48
An: Cesar Troncoso
Cc: users(a)lists.openser.org
Betreff: Re: AW: [OpenSER-Users] XMPP/SIP-SIMPLE Problem
Hello,
On 07/24/08 15:41, Cesar Troncoso wrote:
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
You have to filter only messages with text/plain. Check the Content-Type
header value in the script before calling xmpp functions.
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.
please update to 1.3.2, there was a fix related to same issue and don't
know if was backported. However, could be something else, but it is
better if you work on latest stable, otherwise troubleshooting is hard
to do. 1.2.x is not really maintained as we approach time for 1.4.
By the way,does the xmpp module support presence or is it just meant for IM?
presence gatewaying is supported to some extent, in experimental for via
pua_xmpp.
Please update to 1.3.x, do some tests and let me know if works.
Cheers,
Daniel
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:
--
Daniel-Constantin Mierla
http://www.asipto.com
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