[Diggory Laycock]

Hi,

My powerbook's copy of iChat has gone bad in some way - and I was wondering if anyone can help me diagnose it:

I can do text chats fine - but cannot do Audio chats or Video chats.

The behaviour is the same whether I am connecting to a rendezvous machine on my LAN or someone on another continent.

I connect to the net via Airport Extreme and do not have the Firewall running. I don't use NAT. I have a static IP.


Here is what happens: (The tv pics are because my other machine has a formac studio attached (which iChat sees a a web cam))

If I try to initiate the connection I get this on my powerbook when they accept:

"Failed to start because the other party cancelled" (this is not true)

and the other party sees this:

"Failed to start because the other party (i.e. me) did not respond "


If the other party initiates the connection and I accept then we get the reverse:

I see this:


They get this:



The initiating party gets this in their "Connection Doctor" window: (where <> means I have obscured the relevant info.)

"2004-09-30 14:11:34 +0100: <Name of other party> cancelled the connection
Tried to send UDP SIP "invite" to the following IP addresses and ports:
<IP Address Of Other Party>:5060"

I've repaired the disk privileges, trashed the iChat prefs and re-installed iChat - but to no avail.


Any ideas what's going on here?

[philm]

Has this suddenly happened? Everything was working OK yesterday, kind-of-thing? Has something of a firewall feel to it, but you say no firewall is running. Is this the case for both Macs? In my experience, you get those sorts of error messages for a wide variety of problems, and they are not helpful. (Rather like this reply, perhaps).

[Diggory Laycock]

Originally posted by philm:
... and they are not helpful. (Rather like this reply, perhaps).

What is it about posting here that means you work it out for yourself just afterwards?

I suppose it has something to do with expressing the problem logically in order to type it.

It was my VOIP softphone that was hogging the ports.

SIP - I should have known. A bit boring that I have to quit X-Lite before chats - but at least I know what it was now.

The problem must have been going on for about a month or two now - funny how I never connected the timing with how long I've had a VOIP number.