Damien,I have had the failure below 3 times, this time I managed tocatch it in the log.
It does not seem to occur after any specific period.
1) Started ekiga -d 4 > output.txt 2>&1, it ran for nearly 24hours.2) The icon in the tray disappeared and I was left with a window that looked like the attached(hope that is ok).
3) Below is the last bit of the log(doctored). ekiga restarts fine. Brian2009/01/05 14:16:05.661 13:32:03.106 ekiga OpalUDP Writing to interface 0 - "192.168.1.5%wlan0" 2009/01/05 14:16:05.661 13:32:03.106 ekiga SIP Expiry time for PUBLISH set to 300 seconds. 2009/01/05 14:16:05.661 13:32:03.106 ekiga SIP Transaction created. 2009/01/05 14:16:05.663 13:32:03.108 ekiga DNS SRV Lookup sip.internode.on.net service _sip._udp 2009/01/05 14:16:05.676 13:32:03.121 ekiga SIP Transaction remote address is udp$203.2.134.1:5060 2009/01/05 14:16:05.677 13:32:03.122 ekiga SIP Sending PDU (862 bytes) to: rem=udp$203.2.99.1:5060,local=udp$192.168.0.99:5065,if=192.168.1.5%wlan0
PUBLISH sip:0200...@sip.internode.on.net SIP/2.0 CSeq: 2268 PUBLISHVia: SIP/2.0/UDP 192.168.0.99:5065;branch=z9hG4bK1085633d-4dd9-dd11-9476-001b11e9b188;rport
User-Agent: Ekiga/3.0.1From: <sip:0299...@sip.internode.net>;tag=f081633d-4dd9-dd11-9476-001b11e9b188
Call-ID: 4267633d-4dd9-dd11-9476-001b11e9b...@l2 To: <sip:02999...@sip.internode.net> Contact: <sip:02000...@192.168.0.99:5065> Expires: 300 Event: presence Content-Type: application/pidf+xml Content-Length: 341 Max-Forwards: 70 <?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:0299...@sip.internode.net">
<tuple id="02999...@sip.internode.net"> <note>online</note> <status> <basic>open</basic> </status> <contact priority="1">sip:02999...@sip.internode.net</contact> </tuple> </presence>2009/01/05 14:16:05.677 13:32:03.122 ekiga SIP Transaction timers set: retry=0.500, completion=6.000 2009/01/05 14:16:05.739 13:32:03.184 Opal Liste...0xb5314b90 OpalUDP Binding to interface: 192.168.0.99:5065 2009/01/05 14:16:05.739 13:32:03.184 Opal Liste...0xb5314b90 SIP Waiting for PDU on udp$203.2.134.1:5060<if=udp$192.168.0.99:5065> 2009/01/05 14:16:05.740 13:32:03.185 Opal Liste...0xb5314b90 SIP No Content-Length present from udp$203.2.134.1:5060<if=udp$192.168.0.99:5065>, reading till end of datagram/stream. 2009/01/05 14:16:05.740 13:32:03.185 Opal Liste...0xb5314b90 SIP PDU received: rem=udp$203.2.134.1:5060,local=udp$192.168.0.99:5065,if=192.168.1.5%wlan0
SIP/2.0 405 Method Not Allowed CSeq: 2268 PUBLISHVia: SIP/2.0/UDP 192.168.0.99:5065;received=202.78.39.88;branch=z9hG4bK1085633d-4dd9-dd11-9476-001b11e9b188;rport=5065 From: <sip:02999...@sip.internode.net>;tag=f081633d-4dd9-dd11-9476-001b11e9b188
Call-ID: 4267633d-4dd9-dd11-9476-001b11e9b...@l2 To: <sip:02999...@sip.internode.net>;tag=aprqngfrt-s62bcj30002od Allow: INVITE,ACK,BYE,REGISTER,CANCEL,PRACK,INFO,SUBSCRIBE,NOTIFY,UPDATE2009/01/05 14:16:05.740 13:32:03.186 Opal Liste...0xb5314b90 SIP Transaction 2268 PUBLISH completed. 2009/01/05 14:16:05.741 13:32:03.186 Opal Liste...0xb5314b90 SIP Not retrying PUBLISH due to error response 405 Method Not Allowed
THIS IS THE END OF THE LOG -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
<<attachment: ekiga_bad_window.png>>
_______________________________________________ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list