On 3/8/06, Wendell Turner <[EMAIL PROTECTED]> wrote:
> However, I can't get the key/register to illuminate from a
> 'remote' system.  I can login to the remote jabberd, and issue a
> Service Discover to the other jabberd (the one with the PyMSNt),
> and see the MSN Transport, but the register key does not
> illuminate.  Is this a permission problem?  Is this function
> even allowed?  Can I allow that activity via something in the
> xml configs?

You need to set up a s2s dns entry for the msn transport to point to
the server that the component is connected to.  This allows enternal
users to access the transport.

--
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Wed Mar  8 21:50:31 2006
From: [EMAIL PROTECTED] (Wendell Turner)
Date: Wed Mar  8 21:50:33 2006
Subject: [py-transports] jabberd as 'router'?
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Wed, Mar 08, 2006 at 11:31:04PM +0200, Norman Rasmussen wrote:
> On 3/8/06, Wendell Turner <[EMAIL PROTECTED]> wrote:
> > However, I can't get the key/register to illuminate from a
> > 'remote' system.
> 
> You need to set up a s2s dns entry for the msn transport to point to
> the server that the component is connected to.  This allows enternal
> users to access the transport.

Umm, thank you for the quick response, but I don't follow.

Do I need to change the system dns (e.g., bind) as suggested in
the DNS SRV Records section of the Jabberd 1.4 Admin guide?  Or
edit the jabberd.xml <service id="s2s"> part to specify its own
name or that of the PyMSNt transport?  Or PyMSNt's config.xml to
tell it to allow external access?  This is all on the system
where the jabberd+PyMSNt runs, right?

Thanks again,

Wendell

Reply via email to