Hi Norman,

Here is the answer of  your questions:

1.Which version of pyyimt are you using (also which server & version
are you
 using)?

- I am using the latest available source : yahoo-transport-0.4.tar.gz
and xmpp source: xmpppy-0.4.1
and built it on Solaris 10 Sparc Machine.

We have our own XMPP compliant server product, It behaves properly
with other gateways and gets the disco.


2. What's the value of jid in the config file? (it should be
yim.india.myorg.com)
Right - I think without correct JID and password it would not have
done handshake itself.

Please see the configuration settings below :

Thanks and regards,
-Pravin
###############Config.xml content##########
<?xml version="1.0" ?>
<pyyimt>
    <!-- This file contains options to be configured by the server
administrator. -->
    <!-- Please read through all the options in this file -->

    <!-- The JabberID of the transport -->
    <jid>yim.india.myorg.com</jid>

    <!-- The JabberID of the conference room handler. -->
    <confjid>muc.india.myorg.com</confjid>

    <!-- The component JID of the transport. Unless you're doing
clustering, leave this alone -->
    <!-- <compjid>yahoo1</compjid> -->

    <!-- The public IP or DNS name of the machine the transport is
running on -->
    <!-- This is used to select the outgoing IP address used to
connect to the Yahoo! network -->
    <!--  otherwise known as the vanity address, it's safe to leave it
commented -->
    <!--<host>vanity.host.example.net</host>-->

    <!-- The name of the transport in the service discovery list. -->
    <discoName>Yahoo! Transport</discoName>

    <!-- The location of the spool file.. if relative, relative to the
PyYIMt dir. -->
    <!-- Include the jid of the transport, if running multiple copies
of the same transport -->
    <spoolFile>yahoouser.dbm</spoolFile>

    <!-- The location of the PID file, relative to the PyYIMt
directory -->
    <!-- Comment out if you do not want a PID file -->
    <pid>PyYIMt.pid</pid>

    <!-- The IP address or DNS name of the main Jabber server -->
    <mainServer>mymachine.india.myorg.com</mainServer>

    <!-- The JID of the main Jabber server -->
    <mainServerJID>mymachine.india.myorg.com</mainServerJID>

    <!-- The TCP port to connect to the Jabber server on (this is the
default for Jabberd2) -->
    <port>5269</port>

    <!-- The authentication token to use when connecting to the Jabber
server -->
    <secret>changeit</secret>

    <!-- SASL username used to bind to Jabber server. -->
    <!-- secret, above, is used for sasl password -->
    <!--<saslUsername>username-for-jabberd2-connection</saslUsername>--
>

    <!-- Allow users to register with this transport -->
    <allowRegister/>

    <!-- Allow users to use the Yahoo! chat rooms with this transport
-->
    <enableChatrooms/>

    <!-- Use external component binding. -->
    <!-- This dodges the need to manually configure all jids that talk
to this transport. -->
    <!-- Jabberd2 requires saslUsername and useRouteWrap for this to
work. -->
    <!-- Wildfire as of 2.6.0 requires just this. -->
    <!--<useComponentBinding/>-->

    <!-- Wrap stanzas in <route> stanza. -->
    <!-- Jabberd2 requires this for useComponentBinding. -->
    <!--<useRouteWrap/>-->

    <!-- You can choose which users you wish to have as
administrators. These users can perform some tasks with Ad-Hoc
commands that others cannot -->
    <!--<admins>
        <jid>[EMAIL PROTECTED]</jid>
        <jid>[EMAIL PROTECTED]</jid>
    </admins>-->

    <!-- The file to log to. Leave this disabled for stdout only -->
    <debugFile>yahooerror.log</debugFile>

    <!-- Show the raw data being sent and received from the xmpp and
yahoo servers -->
        <dumpProtocol/>

</pyyimt>


On Aug 29, 5:01 pm, "Norman Rasmussen" <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 29, 2008 at 1:42 PM, Pravin sinha <[EMAIL PROTECTED]> wrote:
> > It looks like PyYIMt does not support disco query. After the handshake when
> > the XMPP server asks for disco, the gateway says that "The feature requested
> > is not implemented by the recipient or server and therefore cannot be
> > processed.".
>
> > It looks like the message is from xmpppy. Please suggest me how can we make
> > it work.(We need this disco result and can't proceed without).
>
> > Can this be fixed if the problem is in implementation or even can you point
> > me a suggested fix for this. I don't think it is a configuration issue as
> > the handshake happened properly. Also I have enabled this disco option
> > <discoName>Yahoo! Transport</discoName>. The same feature works fine for the
> > other two(PyMSNt and PyAIMt).
>
> > Please see the raw dump below.
> > Much appreciate your time and help.
>
> Which version of pyyimt are you using (also which server & version are you
> using)?
>
> What's the value of jid in the config file? (it should be
> yim.india.myorg.com)
>
> The discoName configuration value is only to override the default, if you
> don't enabled it disco will still work.
>
> The disco#info should 'just-work', e.g. here's a dump from my server:
>
> <iq xmlns='jabber:client' type='get' to='yahoo.jabber.example.net'
> id='ac22a' from='[EMAIL PROTECTED]/Psi'>
>     <query xmlns='http://jabber.org/protocol/disco#info'/>
> </iq>
>
> <iq xmlns="jabber:client" to="[EMAIL PROTECTED]/Psi" from="
> yahoo.jabber.example.net" id="ac22a" type="result">
>     <query xmlns="http://jabber.org/protocol/disco#info";>
>         <identity category="gateway" type="yahoo" name="Yahoo! Transport" />
>         <feature var="jabber:iq:register" />
>         <feature var="jabber:iq:version" />
>         <feature var="http://jabber.org/protocol/commands"; />
>         <feature var="jabber:iq:avatar" />
>         <feature var="http://jabber.org/protocol/chatstates"; />
>     </query>
> </iq>
>
> --
> - Norman Rasmussen
> - Email: [EMAIL PROTECTED]
> - Home page:http://norman.rasmussen.co.za/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to