[JDEV] Delivery error when setting up for new transport

[Migs Paraz]

Hi,
I'm writing a Python SMS component based on the sample code.
But, the server rejects the client when logging in.  

I've only added:

      <browse>

        <service type="sms" jid="sms.localhost" name="SMS Gateway">
          <ns>jabber:iq:gateway</ns>
        </service>

and:

  <service id="sms">
    <host>localhost</host>
    <accept>
      <ip>127.0.0.1</ip>
      <port>1234</port>
      <secret>test</secret>
    </accept>
  </service>


The errors:

Wed Dec 12 15:00:26 2001  mio.c:750 MIO read from socket 11: <iq id='A0' type='get'><query xmlns='jabber:iq:auth'><username>baloney</username></query></iq>
Wed Dec 12 15:00:26 2001  client.c:243 pthsock_client_read called with: m:8109A68 flag:3 arg:8109B58
Wed Dec 12 15:00:26 2001  deliver.c:460 DELIVER 4:localhost <route type='auth' to='baloney at localhost' from='11 at c2s/8109A68'><iq id='A0' type='get'><query xmlns='jabber:iq:auth'><username>baloney</username></query></iq></route>
Wed Dec 12 15:00:26 2001  deliver.c:579 delivery failed (Unable to deliver, destination unknown)
Wed Dec 12 15:00:26 2001  log.c:105 <log type='notice' from='localhost'>bouncing a routed packet to baloney at localhost from 11 at c2s/8109A68: Unable to deliver, destination unknown</log>
Wed Dec 12 15:00:26 2001  deliver.c:460 DELIVER 3:localhost <log type='notice' from='localhost'>bouncing a routed packet to baloney at localhost from 11 at c2s/8109A68: Unable to deliver, destination unknown</log>
Wed Dec 12 15:00:26 2001  deliver.c:651 delivering to instance 'elogger'
20011212T07:00:26: [notice] (localhost): bouncing a routed packet to baloney at localhost from 11 at c2s/8109A68: Unable to deliver, destination unknown
Wed Dec 12 15:00:26 2001  deliver.c:460 DELIVER 4:c2s <route type='error' to='11 at c2s/8109A68' from='baloney at localhost' error='Unable to deliver, destination unknown'><iq id='A0' type='get'><query xmlns='jabber:iq:auth'><username>baloney</username></query></iq></route>


When I remove my additions to the config file, these errors go away.
What causes these?
I don't have this problem with the JUD transport I wrote earlier.

I'd appreciate help here so I can go on with writing my transport...