Ralph Johns UK

Actually original page 4 contained so much and needed clarity regarding the New Error logs for iChat 3.1.5
Part 2 deals with the areas covered by the links listed below which are in fact Intra-page links

Jump to The Text in A Box (SIP Issues)
Jump to Connection Problems

SIP Protocol

• This is a protocol that iChat uses to instigate Video and Audio chats and needs to be able to do this on port 5060. If you use any form of SIP phone or Voice over IP software you may also need to look into it causing problems as well as checking if the router is SIP aware.

1. The device is SIP aware. SIP is a text based protocol to enable IP phones to connect and use the internet. This protocol uses port 5060. iChat also uses this Protocol within the UDP data on port 5060.


2. The ISP offers SIP as a separate paid for Service. (They Block port 5060 until you pay). Unfortunately as Apple's market share is still relatively small (and iChat's is relistically smaller still) ISP are reluctant to do mauch about this or at least seem not to care they block other Applications by doing this

If this is the cause you will not be able to Video or Audio only chat.

The solution is to speak to your ISP and find out if they are blocking any ports at their level. Negociate to get the port(s) open.

The Utilities on a Mac can not Port Scan on the UDP protocol. Download IPNetMonitorX from this link (The icon is the download button) It will run as a trial fro a few days. Long enough for you to test. The process is:- Find a friendly Buddy who will tell you their Public IP
Select UDP Port Scan after opening the Utility.
Type in the IP to test against.
Scan port 5060
If you get the message " No Response" then the port is blocked somewhere between the two of you.
Check the scan to the IP of your Modem and any router you have to check it is not your end.
Try other Buddies to eliminate further
If you know the ISP server IP that gives you your IP test against that as well

You should now have enough information to say to the ISP you know they are Blocking the 5060 port.

Symptoms of SIP Binding on the Modem.

Unfortunately this appears as an intermittent problem affecting some Buddies that you contact.

• Some, a small group, you can contact all the time.
  
• Another small group you can connect to now and then.
  
• The largest group of your Buddies you can not connect to at all.

• 2005-03-08 18:34:32 +0000: xxx did not respond. Tried to send UDP SIP "invite" to the following IP addresses and ports:
  136.xxx.xxx.xxx:5060 192.168.0.2:5060
  

In iChat 3 in OS 10.4.7 and above you will get an Error 8 log

• 136.xxx.xxx.xxx:5060

Back to ISP and VoIP related stuff for a moment

If your ISP offers such a service or you have an application that can dial other internet or landline phones (Skype for instance) you may need to check if this is the cause of your problem. Try turning off any such applications.

Vonage and similar adapters.
These are used to make landline phones work over the internet. Often the adpater is placed between the modem and the computer and handles SIP traffic (Directed to the Phone hence the problem).

A solution is to move the adapter to the same level as the computer.

• Modem < - > Router <: - > Computer and adapter

Unbinding SIP

Starting with Version 4 or less firmware

This may not be an option you can change in the browser interface with your modem. It is possible to Telnet them some from Terminal (or other Command Line Interface).

Only do this if you do not have an IP phone. Only a few modems will have this as a setting you can change in the set up pages accessed from your Browser. There are in fact other ways you can access your modem. One of these is with a Telnet command. This has to be done from an application or Utility that can issue Command Line Interface (CLI) instructions. Your ever helpful Mac has such a Utility. It is called Terminal. It is found in Applications/Utilities on your Harddrive.

So open Terminal. It will look like this:-

Welcome to Darwin!
Ralph:~ Ralph$

It will show your (short) name instead of mine obviously !

You need to enter the instructions I have laid out in the Text Box below. Scroll down until you can see the purple box below the White one. This shows all the entries made on my Alcatel with the entries Bolded. The "picture" only showsa like this if the window is dragged big enough to see all of it. You may only see a few lines just above where you are making entries if the window is small.

Oh yes !! It is also case sensitive !! Everything in lower case except for SIP when it is input.

Like this

Welcome to Darwin!
Ralph:~ Ralph$ telnet 10.0.0.138
Trying 10.0.0.138...
Connected to speedtouch.lan.
Escape character is '^]'.
Username : ( hit enter here if no Password )
------------------------------------------------------------------------
*
*                             ______  SpeedTouch 510
*                         ___/_____/\ 
*                        /         /\\  Version 4.2.5.0.0
*                  _____/__       /  \\ 
*                _/       /\_____/___ \  Copyright (c) 1999-2003, 
*               //       /  \       /\ \              THOMSON
*       _______//_______/    \     / _\/______ 
*      /      / \       \    /    / /        /\
*   __/      /   \       \  /    / /        / _\__ 
*  / /      /     \_______\/    / /        / /   /\
* /_/______/___________________/ /________/ /___/  \ 
* \ \      \    ___________    \ \        \ \   \  /
*  \_\      \  /          /\    \ \        \ \___\/
*     \      \/          /  \    \ \        \  /
*      \_____/          /    \    \ \________\/
*           /__________/      \    \  /
*           \   _____  \      /_____\/
*            \ /    /\  \    /___\/
*             /____/  \  \  /
*             \    \  /___\/
*              \____\/
*
------------------------------------------------------------------------
=>nat unbind
application = SIP
port = 5060
[port_end] = 5060
:nat unbind application=SIP port=sip port_end=sip
Failed to delete NAT binding on port 5060 : the binding doesn't exist.

If this has not been done before then the last two lines will not appear.

Quitting Terminal is at least one way of ending the Terminal Session.

Variation for a Version 5 Firmware device according to Speedtouch.co.uk

(0906 3022114 - is the advertised number on their web page 
- http://www.speedtouch.co.uk/ - 
though SAYNOTO0870.com help with a non premium rate 02073090226)

They sent back the following text

For your firmware version: (EDIT: The Terminal bit)

Start the telnet session (telnet 192.168.1.254)
Username: admin
password : ????
On the command prompt enter:
-------------------------------------------------------------
connection unbind application=SIP port=5060 <enter>
saveall <enter>
-------------------------------------------------------------

Or with the menu: (EDIT: Like the above Version 4 Firmware but menus

It is a sort of click this and go method using arrow keys Tab and enter

Small amount of typing.)
-------------------------------------------------
on the prompt:   	(use the Arrow keys and Tab for Ok or Cancel)
menu <enter>
goto <connections> <enter>
goto <unbind> <enter>
fill in :
Application: SIP
port : 5060
press <Tab> to goto <OK>
press <Tab> to goto <Cancel>
on the prompt type in:
saveall <enter>
----------------------------------------------------

The BT HOME HUB

If you are still having problems it may pay to start from fairly near the begining again. Don't presume that you got it right. Double check. One of the things I often go through on the Apple Discussions about iChat is asking those simple questions again.

"Have you done the Quicktime Setting ?"

"Is the Bandwidth Limit drop down set to NONE ?"

"Is the Mac Firewall On and have you set the Ports there ?"

"Have you opened the ports in your modem and any separate router ?"

Sometimes I am convinced some people need to hear the question phrased differently or sometimes you just have to "tell them three times".

Care should be taken to ensure the ports are open to the correct protocols. See the requirements in the Apple Doc 93208. Whatever means you use - these ports have to open. The style shown in the Apple Doc lends itself mainly towards to Port Forwarding. If you use Port Triggering these same ports will need to appear somewhere in your set up. Not all devices will require the protocols to be set, in Port Forwarding or in some cases Port Triggering.

Firmware

As these two pages (4 and 4a) deal with problems with connecting it is worth considering whether you have an older device with it's original Firmware. This Firmware is the software that makes your Modem or router work. An older device can get a whole new lease of life and solve some issues if the Firmware is updated.

Finding links for your device may be difficult via a manufactures web pages if your device is out of manufucture. I found a link on ADSL Guide link when I couldn't see one on the Alcatel site.

This is fairly broad brush information which I have tried to keep fairly simple. Or rather have tried to explain simply which is not the same thing.

This is not a step by step approach as there are just too many routers and modems. You will have to read around the information about your device.

Soem of the more popular ones are found at these links.

For Linksys

For Netgear

For Speedstream

For help with Port Forwarding and Trigger port settings; Port Forwarding.com The Port Triggering list (Of capable devices) is accessed form this page as one of the options near the top. I would only recommend this site for Instruction to access the Device and the method of setting the ports as the actual ports are listed incorrectly.

Why is this bit here and in this format ?

Well it partly because of the way the pages grew out of the original info I put up here. I also beleive in the "Tell them three ways/times" method of passing information. Some pages are particularly wordy, some have more pictures to help, most fit somewhere in-between. However It never hurts to rephrase things now and then. So here goes with this sort of follow-up-review of things if pages 4 and 4a have not helped so far.

Start Here

If you can not Audio or Video chat to someone in your Buddy list who you can text to it is likely that the problem falls into one of three areas. (presuming you/they fit the criteria of camera or mic)

1. Firstly that your uplink DSL speed is not suffient. A basic option of DSL should have an uplink speed of 128kbps at least. In some countries this is described as the lower limit of "Broadband". (Internationally "Broadband" does not really start until a 256k speed is reached) Anything lower can produce blocky pics and unsynched sound with Video connections. iChat will report an unsustainable connection if the speed drops below 50kbps.

   Solution
   

   1. Upgrade your link.
   
   
   2. Go to iChat Preferences and in the Video section select NONE as the Bandwidth limit in the Bandwidth drop down. The iChat appliction will balance the Video and Audio parts of the ouptput. You need to have the Connection Doctor open (from the Video menu), to see the results in the Bit rate. Make sure it does not drop below 100.
   
   
   3. Go to System Preferences > Quicktime > Connection speed or Streaming Tab (depending on Quicktime version). Set the speed in the drop down to matych your Download speed
   
   
   4. Test your Connection Speed to see if you are getting what you paid for
   
   

2. Secondly
   That your computer is a G3/500 or less. Apple state G3/600 is minimum. This is around the later models of the Bubble shapped Orignal iMac design. A Firewire Port is Quoted as a requirment, but read the Solution area.
   
   Apple Doc 301050 descibes the new needs of Tiger and iChat 3.x

   Solution

   1. Download this utility: iChatUSBCam that enables slower machine and USB cameras to be used.
      It comes with a 7 day free trial version.
      

      iChat 3 Please note there is a now a combined version on that page that works for Panther/iChat2.x and Tiger/iChat 3.x

      
      Some people on the Apple iChat Discussion area have reported that it also improves the functioning of G3 Macs in the range 600 - 900 Mghz
   
   Sub issues around this USB problem appear to be:
   • High usage of processor by other apps. (don't forget USB devices)
   
   
   • High usage of Network savvy apps (don't forget iTunes and iPhoto in certain countries).
   
   
   • Low levels of RAM.
   
   
   2. Upgrade your Computer :-)

3. Thirdly
   Somewhat related to both, is the fact that you could be running more than one computer on your Internet link, using up bandwidth.

   Solution

   1. Shut down other computers.
      (NOTE: I have managed to run two computers, using different AIM screen names, over the same DSL link. I.E. Out of the house > AIM server > back to other computer without bandwidth problems. I then had a 1Mb download but only 256kbps Uplink.)
   
   
   2. Try Audio first to see if you can connect. This eliminates most bandwidth and computer usage problems. If this doesn't work then the router/modem or ports in the Mac Firewall if On are the likely areas to concentrate on.
   
   
   3. Make sure both computers have done the Quicktime setting and have the Bandwidth set to NONE
   
   
   4. Upgrade your connection if you can.

From reading around it would appear that routers list that they can either "NAT" or "NAPT" or "PAT". These will essentially be the same thing, or variations used with Port Forwarding, DMZ or Port Triggering but it does appear for iChat that there can be problems for this area.

My knowledge of things Networking are vague (but improving) and you may want to read elsewhere for more detail. Having said that, it appears that not all routers perform Network Address Translation the same way and in some cases the two devices involved do not communicate properly, which I tend to refer to on the Apple Discussion pages as 'not playing nicely together'. This can lead to the situation where 1 out of a group of 3 people finds that they can not Video or Audio chat to other memebers of the group. The only 2 practical solutions I found are:-

1. Change to using UPnP where you can

2. Try a different router/Modem at one of the locations, after trying without Port Forwarding/NAT (include DMZ And Port Triggering).

In brief.
Routers pass information (data) in the form of packets. These packets can be sent using different protocols. Basically router are hardware firewalls and the doors (ports) have to be open to let information pass). TCP and UDP are the main ones but iChat AV also uses SIP (within the data on port 5060). SIP is also used with Voice over IP applications. See note 4 in the document list in the first link of this section. It's near the bottom of that Apple Doc.

Error Messages in 10.4.7

As you probably came to this page or page 4 looking for something about the Error logs of 10.4.7 and above. This bit below is from a longer section on page 16a.

I have given a great deal of thought to whether to include it due to the complexity of trying to explain it.... But here goes....

In it's usual manner of not actually saying they are aware of a problem, Apple have added a "Feature" to iChat at the 10.4.7 update that produces a Log file that can then be sent to Apple. It is specific to A/V chats.

What happens is the chat fails and a slide out window appears with a message about improving iChat with the info. There are two buttons at the bottom for Sending to Apple or not. Once the message is dealt with the window appears and you are left with just the Video Chat window (I say Video because that is where it is most reported) with the same message it always had. The actual message varies depending on the cause.

On the Log window there is a "Details" reveal triangle. Clicking on this will show you the actual log and the eror code. They are made up of three parts as coloured here.

Date/Time:      2006-07-05 21:11:03.403 +0100
OS Version:     10.4.7 (Build 8J135)
Report Version: 4

iChat Connection Log:
AVChat started with ID 485234091.
ralphjohnsuk1: State change from AVChatNoState to AVChatStateWaiting.
0x157a780: State change from AVChatNoState to AVChatStateInvited.
0x157a780: State change from AVChatStateInvited to AVChatStateConnecting.
[Edit Name]: State change from AVChatStateWaiting to AVChatStateConnecting.
[Edit Name]: State change from AVChatStateConnecting to AVChatStateEnded.
Chat ended with error -8
0x157a780: State change from AVChatStateConnecting to AVChatStateEnded.
Chat ended with error -8

Video Conference Error Report:


Video Conference Support Report:


Video Conference User Report:


Binary Images Description for "iChat":
0x1000 - 0x170fff com.apple.iChat 3.1.5 (436) /applications/iChat.app/Contents/MacOS/iChat
[EDIT]

Video Conference Error Report:


Video Conference Support Report:


Video Conference User Report:

There are four common error code numbers and these relate to the actual message on the failed Video Chat window.

Section Links

• SIP


A bit about SIP and how iChat uses it.

Also of course some of the things you might have to check and what to do about sorting them out.


• Unbinding SIP


This works with certain Modems that are SIP Aware.
The list inclueds Thomson- Alcatels 500 Series and some Draytecks


• Connection Problems


Like what it says - A review of info from Pages 3 and 4


• Error Log codes


A start of info about the Error Logs numbers that have come about from the 10.4.7 update