[Users] connect xmpp component to jabber xcp?
Daniel-Constantin Mierla
daniel at voice-system.ro
Wed Apr 18 14:00:03 CEST 2007
Hello,
seems that the connection is closed by Jabber/XMPP server. Can you run
it in debug mode and see the logs there?
Cheers,
Daniel
On 04/17/07 20:49, Matt Winter wrote:
> Please note, the default port setting which the xmpp module is
> attempting to connect to the jabber server is 5347. This port was not
> open on the jabber xcp server, so we configured an additional XMPP
> director to listen on 5347. The result is a failed attempt to connect to
> the jabber server. Thanks.
>
> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592
> 0(0) DEBUG: udp_init: trying SO_RCVBUF: 221184
> 0(0) DEBUG: setting SO_RCVBUF; set=221184,verify=221184
> 0(0) DEBUG: udp_init: trying SO_RCVBUF: 223232
> 0(0) DEBUG: setting SO_RCVBUF; set=223232,verify=221184
> 0(0) DEBUG: setting SO_RCVBUF has no effect
> 0(0) INFO: udp_init: SO_RCVBUF is finally 221184
> 0(0) init_unixsock_socket: No unix domain socket will be opened
> 1(20139) DEBUG:init_mod_child: PROC_TIMER , rank=-1, module=tm
> 1(20139) DEBUG: callid: '3f7d2fd0-20139 at 10.1.1.254'
> 1(20139) DEBUG:init_mod_child: PROC_TIMER , rank=-1, module=mi_fifo
> 1(20139) DEBUG:init_mod_child: PROC_TIMER , rank=-1, module=xmpp
> 1(20139) xmpp: child_init: initializing child <-1>
> 1(20139) DBUG:run_timer: tv = 0, 100000 , m=10
> 0(20138) DEBUG:init_mod_child: CHILD , rank=1, module=tm
> 0(20138) DEBUG: callid: '3f7d2fd0-20138 at 10.1.1.254'
> 0(20138) DEBUG:init_mod_child: CHILD , rank=1, module=mi_fifo
> 0(20138) DEBUG:mi_fifo:mi_child_init: new process with pid = 20140
> created.
> 0(20138) DEBUG:mi_fifo:mi_init_fifo_server: FIFO created @
> /tmp/openser_fifo_xmpp
> 0(20138) DEBUG:mi_fifo:mi_init_fifo_server: fifo /tmp/openser_fifo_xmpp
> opened, mode=660
> 0(20138) INFO:mi_fifo:mi_child_init(1): extra fifo listener processes
> created
> 0(20138) DEBUG:init_mod_child: CHILD , rank=1, module=xmpp
> 0(20138) xmpp: child_init: initializing child <1>
> 0(20138) xmpp: started child connection process
> 0(20138) xmpp: resolving jabbersrv.corp.viack.com...
> 0(20138) xmpp: connecting to 10.1.1.78:5347...
> 0(20138) xmpp: connected to 10.1.1.78:5347...
> 0(20138) xmpp: net_printf: [<?xml version='1.0'?><stream:stream
> xmlns='jabber:component:accept' to='xmpp.jabbersrv.corp.viack.com'
> --------repeats------------------------
> version='1.0' xmlns:stream='http://etherx.jabber.org/streams'>]
> 0(20138) xmpp: recv() error: Connection reset by peer
> 0(20138) xmpp: resolving jabbersrv.corp.viack.com...
> 0(20138) xmpp: connecting to 10.1.1.78:5347...
> 0(20138) xmpp: connected to 10.1.1.78:5347...
> 0(20138) xmpp: net_printf: [<?xml version='1.0'?><stream:stream
> xmlns='jabber:component:accept' to='xmpp.jabbersrv.corp.viack.com'
> --------repeats------------------------
> version='1.0' xmlns:stream='http://etherx.jabber.org/streams'>]
> 0(20138) xmpp: recv() error: Connection reset by peer
>
>
>
> -----Original Message-----
> From: Daniel-Constantin Mierla [mailto:daniel at voice-system.ro]
> Sent: Tuesday, April 17, 2007 5:46 AM
> To: Matt Winter
> Cc: users at openser.org
> Subject: Re: [Users] connect xmpp component to jabber xcp?
>
> Hello,
>
> can you post relevant debug messages?
>
> Cheers,
> Daniel
>
>
> On 04/16/07 23:41, Matt Winter wrote:
>
>> Hello,
>> I'm having a problem connecting my openser xmpp module(in component
>> mode) to a jabber xcp server. Has anyone done this?
>>
>> Here's my openser.cfg file. Thanks.
>>
>> # more /etc/openser/openser.cfg
>> #
>> # $Id: openser-xmpp.cfg 1827 2007-03-12 15:22:53Z bogdan_iancu $
>> #
>> # simple quick-start config script for XMPP GW
>> #
>> # make sure in your main SIP server that you send
>> # only the adequate SIP MESSAGES to XMPP GW
>> #
>> #
>> # ----------- global configuration parameters ------------------------
>>
>> debug=9 # debug level (cmd line: -dddddddddd)
>> fork=no
>> log_stderror=yes # (cmd line: -E)
>>
>> /* Uncomment these lines to enter debugging mode
>> fork=no
>> log_stderror=yes
>> */
>>
>> check_via=no # (cmd. line: -v)
>> dns=no # (cmd. line: -r)
>> rev_dns=no # (cmd. line: -R)
>> children=4
>>
>> listen=udp:10.1.1.234:5060
>> alias=xmpp.jabbersrv.corp.com
>>
>> # ------------------ module loading ----------------------------------
>>
>> mpath="/lib/openser/modules/"
>> loadmodule "sl.so"
>> loadmodule "tm.so"
>> loadmodule "rr.so"
>> loadmodule "maxfwd.so"
>> loadmodule "textops.so"
>> loadmodule "mi_fifo.so"
>>
>>
>> # XMPP
>> loadmodule "xmpp.so"
>>
>> modparam("xmpp", "domain_separator", "*")
>> modparam("xmpp", "gateway_domain", "xmpp.jabbersrv.corp.com")
>> modparam("xmpp", "xmpp_domain", "xmpp.jabbersrv.corp.com")
>> modparam("xmpp", "xmpp_host", "jabbersrv.corp.com")
>>
>> modparam("xmpp", "backend", "component")
>> modparam("xmpp", "xmpp_password", "BCD11234DC")
>>
>> # ----------------- setting module-specific parameters ---------------
>>
>> # -- mi_fifo params --
>>
>> modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo_xmpp")
>>
>> # -- usrloc params --
>>
>> # -- rr params --
>> # add value to ;lr param to make some broken UAs happy
>> modparam("rr", "enable_full_lr", 1)
>>
>> # ------------------------- request routing logic -------------------
>>
>> # main routing logic
>>
>> route{
>>
>> # initial sanity checks -- messages with
>> # max_forwards==0, or excessively long requests
>> if (!mf_process_maxfwd_header("10")) {
>> sl_send_reply("483","Too Many Hops");
>> exit;
>> };
>>
>> if (msg:len >= 2048 ) {
>> sl_send_reply("513", "Message too big");
>> exit;
>> };
>>
>> ### absorb retransmissions ###
>> if (!t_newtran()) {
>> sl_reply_error();
>> return;
>> }
>> if (method == "MESSAGE") {
>> log("*** xmpp-handled MESSAGE message.\n");
>> if (xmpp_send_message()) {
>> t_reply("200", "Accepted");
>> } else {
>> t_reply("404", "Not found");
>> }
>> return;
>> }
>>
>> log("*** xmpp: unhandled message type\n");
>> t_reply("503", "Service unavailable");
>> return;
>> }
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
>
More information about the Users
mailing list