I can register from kphone no problem. But i cannot register from
shtoom, there isn't even a SIP REGISTER Request that is being sent out
as i can see:
==============
2005-02-24T13:30:29.620608 [-] Log opened.
2005-02-24T13:30:29.646919 [-] <class 'shtoom.sip.SipProtocol'> starting
on 5060
2005-02-24T13:30:29.647313 [-] Starting protocol <shtoom.sip.SipProtocol
object at 0x40a2f5ac>
2005-02-24T13:30:29.647522 [app] sip listener installed on 5060
2005-02-24T13:30:29.669062 [-] <class 'shtoom.upnp.UPnPProtocol'>
starting on 1900
2005-02-24T13:30:29.669435 [-] Starting protocol
<shtoom.upnp.UPnPProtocol object at 0x40a2268c>
2005-02-24T13:30:29.671151 [-] <class 'shtoom.stun._DetectSTUNProt'>
starting on 0
2005-02-24T13:30:29.671837 [-] Starting protocol
<shtoom.stun._DetectSTUNProt object at 0x40b05d4c>
2005-02-24T13:30:29.672534 [sip] no outstanding registrations, registering
2005-02-24T13:30:29.673100 [-]
/usr/lib/python2.3/site-packages/shtoom/sip.py:296:
exceptions.DeprecationWarning: use listenUDP and then transport.connect().
2005-02-24T13:30:29.673311 [-]
twisted.internet.protocol.ConnectedDatagramProtocol starting on 0
2005-02-24T13:30:29.673582 [-] Starting protocol
<twisted.internet.protocol.ConnectedDatagramProtocol instance at
0x40b4d0ac>
2005-02-24T13:30:29.673887 [sip] discovered local address
('192.168.0.8', 5060), remote ('64.52.204.38', 5060)
2005-02-24T13:30:29.674320 [sip] NAT policy says yes, we're transitting
a NAT
2005-02-24T13:30:29.840817 [-]
twisted.internet.protocol.ConnectedDatagramProtocol starting on 0
2005-02-24T13:30:29.841155 [-] Starting protocol
<twisted.internet.protocol.ConnectedDatagramProtocol instance at
0x40b4d3ec>
2005-02-24T13:30:30.048681 [-] (Port 0 Closed)
2005-02-24T13:30:30.048932 [-] Stopping protocol
<twisted.internet.protocol.ConnectedDatagramProtocol instance at
0x40b4d0ac>
2005-02-24T13:30:30.050253 [-] (Port 0 Closed)
2005-02-24T13:30:30.050418 [-] Stopping protocol
<twisted.internet.protocol.ConnectedDatagramProtocol instance at
0x40b4d3ec>
2005-02-24T13:30:30.062625 [stun] got STUN response from ('64.69.76.23',
3478)
2005-02-24T13:30:30.202243 [stun] got unexpected STUN response
'\xd6\x0f\xc5\xbb\xc6\xdf\x93\xd5\x10`\xd5\x115\x94\x9fI' !=
'\x8c\xe1\xfa\x8b\nrn\x9c"\xdf\xab\x1cF\xe0\x97\x1c' from
('64.69.76.23', 3478)
2005-02-24T13:30:30.215056 [stun] got STUN response from ('64.69.76.24',
3479)
2005-02-24T13:30:30.215529 [-] (Port 0 Closed)
2005-02-24T13:30:30.215708 [-] Stopping protocol
<shtoom.stun._DetectSTUNProt object at 0x40b05d4c>
2005-02-24T13:30:30.673730 [UPnP] got a response from ('192.168.0.1',
1900), status 200
2005-02-24T13:30:30.675204 [UPnP] found a UPnP device at
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:30.681011 [UPnP] got a response from ('192.168.0.1',
1900), status 200
2005-02-24T13:30:30.681520 [UPnP] found a UPnP device at
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:30.682906 [UPnP] got a response from ('192.168.0.1',
1900), status 200
2005-02-24T13:30:30.683368 [UPnP] found a UPnP device at
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:30.694981 [UPnP] before
stupidrandomdelaytoworkaroundbug got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:30.710824 [UPnP] before
stupidrandomdelaytoworkaroundbug got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:30.714710 [UPnP] before
stupidrandomdelaytoworkaroundbug got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.695597 [UPnP] after
stupidrandomrelaytoworkaroundbug, got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.705563 [UPnP] you're behind a Microsoft
2005-02-24T13:30:34.706581 [UPnP] upnp response has no urlbase, falling
back to
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.707158 [UPnP] upnp response showed no WANIPConnections
2005-02-24T13:30:34.711567 [UPnP] after
stupidrandomrelaytoworkaroundbug, got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.718826 [UPnP] you're behind a Microsoft
2005-02-24T13:30:34.719757 [UPnP] upnp response has no urlbase, falling
back to
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.720352 [UPnP] upnp response showed no WANIPConnections
2005-02-24T13:30:34.720581 [UPnP] after
stupidrandomrelaytoworkaroundbug, got an IGDevice from
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.728114 [UPnP] you're behind a Microsoft
2005-02-24T13:30:34.729140 [UPnP] upnp response has no urlbase, falling
back to
http://192.168.0.1:2869/upnphost/udhisapi.dll?content=uuid:62001f1d-3b31-4ea5-bd1d-553f09c4c136
2005-02-24T13:30:34.729705 [UPnP] upnp response showed no WANIPConnections
====================
My shtoomrc file looks like:
[shtoom]
audio=oss
[register]
register_uri=sip:XXX.XXX.XXX.XXX:5060
register_user=666
I am surpired that happened because i used shtoom long time ago and as i
recall thing went fine then!
thanks
m.smadi
_______________________________________________
Shtoom mailing list
[email protected]
http://mail.python.org/mailman/listinfo/shtoom
