Video iChat problem using AIM (Routing through 2nd NIC)

Question

routing iChat for AIM
I have a Mac Pro with both ethernet cards connected. ethernet zero is connected to my office network and ethernet one is connected to a back channel DMZ. I do not have Access to the office router and it's been configure to prevent chat. I have added routes to the table for ethernet 1and am able to chat through AIM with my wife on the iMac at the house with no issues. However when I establish a video connection it errors out. I've made sure that I have both the initial and establish connection IP's routing through my back channel. But it doesn't seem to work. If I turned off the office LAN, I have no problem connecting using video chat.
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 172.24.187.251 UGSc 22 288 en0
64 192.168.0.1 UGSc 0 0 en1
74.124/16 192.168.0.1 UGSc 0 0 en1
74.124.211.219/32 192.168.0.1 UGSc 1 0 en1
127 localhost UCS 0 0 lo0
localhost localhost UH 1 608 lo0
169.254 link#4 UCS 0 0 en0
172.24.187/24 link#4 UCS 10 0 en0
gx280image 0:19:b9:12:64:93 UHLW 0 0 en0 1166
minint-fcnjr5if 0:18:8b:1b:26:7e UHLW 0 11 en0 1077
minint-a07t9r69 0:15:c5:7:d9:18 UHLW 0 0 en0 1194
172.24.187.21 localhost UHS 0 194 lo0
172
172.24.187.251 0:0:c:7:ac:82 UHLW 18 427 en0 119
192.168.0 link#5 UCS 8 0 en1
192.168.0.1 0:9:5b:f6:96:ac UHLW 4 9 en1 1151
192.168.0.2 0:6:5b:90:c2:4b UHLW 0 44 en1 1155
192.168.0.17 0:21:e9:93:3:1d UHLW 0 0 en1 1057
192.168.0.23 0:1b:77:12:f0:6a UHLW 0 8 en1 997
192.168.0.25 0:21:e9:65:c6:33 UHLW 0 0 en1 513
192.168.0.44 0:21:e9:8f:23:7c UHLW 0 0 en1 1056
192.168.0.48 localhost UHS 0 7 lo0
192.168.0.255 link#5 UHLWb 1 100 en1
192.168.73 link#8 UC 1 0 vmnet1
192.168.73.255 link#8 UHLWb 1 89 vmnet1
192.168.222 link#7 UC 1 0 vmnet8
192.168.222.255 link#7 UHLWb 1 89 vmnet8
205.188.0/16 192.168.0.1 UGSc 2 0 en1
209.85.201.125/32 192.168.0.1 UGSc 1 0
Show the following established connections when trying to use video chat.
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 192.168.0.48.50922 64.12.30.68.5190 ESTABLISHED
tcp4 0 0 192.168.0.48.50918 205.188.8.179.5190 ESTABLISHED
tcp4 0 0 192.168.0.48.50917 209.85.201.125.5223 ESTABLISHED
tcp4 0 0 172.24.187.21.50915 172.24.195.103.80 ESTABLISHED
tcp4 0 0 172.24.187.21.50914 172.24.195.102.80 ESTABLISHED
tcp4 0 0 192.168.0.48.50227 74.124.211.219.993 ESTABLISHED
tcp4 0 0 192.168.0.48.50225 74.124.211.219.993 ESTABLISHED
tcp4 0 0 192.168.0.48.50223 74.124.211.219.993 ESTABLISHED
tcp4 0 0 192.168.0.48.50221 74.124.211.219.993 ESTABLISHED
udp46 0 0 *.16402 .
udp4 0 0 *.55928 .
udp4 0 0 *.5351 .
udp4 0 0 *.5350 .
udp4 0 0 127.0.0.1.49728 127.0.0.1.49728
udp4 0 0 172.24.187.21.123 .
udp6 0 0 fe80::225:ff:fee.123 .
udp4 0 0 172.24.187.21.138 .
udp4 0 0 172.24.187.21.137 .
udp4 0 0 192.168.0.48.138 .
udp4 0 0 192.168.0.48.137 .
udp4 0 0 192.168.73.1.138 .
udp4 0 0 192.168.73.1.137 .
udp4 0 0 192.168.222.1.138 .
udp4 0 0 192.168.222.1.137 .
udp4 0 0 *.138 .
udp4 0 0 *.137 .
udp4 0 0 *.52460 .
udp4 0 0 *.53118 .
udp4 0 0 *.62551 .
udp4 0 0 *.64698 .
udp4 0 0 *.57696 .
udp4 0 0 *.58110 .
udp4 0 0 *.62845 .
udp4 0 0 *.50647 .
udp4 0 0 *.59899 .
udp4 0 0 *.57346 .
udp4 0 0 *.56231 .
udp4 0 0 *.631 .
udp4 0 0 192.168.0.48.123 .
udp4 0 0 *.60623 .
udp4 0 0 *.60450 .
udp4 0 0 *.64265 .
udp4 0 0 *.49597 .
udp4 0 0 *.54901 .
udp4 0 0 172.24.187.21.49410 .
udp4 0 0 172.24.187.21.49373 .
udp4 0 0 *.2223 .
udp4 0 0 *.53391 .
udp4 0 0 *.64030 .
udp4 0 0 *.57804 .
udp4 0 0 *.56795 .
udp4 0 0 *.54587 .
udp4 0 0 *.62597 .
udp4 0 0 *.61433 .
udp4 0 0 *.49535 .
udp4 0 0 *.50679 .
udp4 0 0 *.49810 .
udp4 0 0 192.168.73.1.123 .
udp4 0 0 192.168.222.1.123 .
udp6 0 0 fe80::223:dfff:f.123 .
udp6 0 0 ::1.123 .
udp4 0 0 127.0.0.1.123 .
udp6 0 0 fe80::1%lo0.123 .
udp6 0 0 *.123 .
udp4 0 0 *.123 .
udp6 0 0 *.5353 .
udp4 0 0 *.5353 .
udp4 0 0 . .
icm4 0 0 . .
icm6 0 0 . .
icm6 0 0 . .
as I said I can still chat, I just cannot use video chat unless I disconnect the office network. I need to leave the office network as the default route. Suggestions would be appreciated, not sure if iChat problem or routing problem.

Answer 1

Umm,
Not so much as a Bug but a feature.
iChat has been designed with a level of security in-built.
When you send a Visible Invite it is just that, away to trigger the other end to pop up a window.
iChat then engages in the SIP part which includes a text based connection method called SIP (Session Initiation Protocol).
This involves a behind the scenes invite and a check to see that the IP the Visible invite went to is the same one the SIP bit ios going to. (remember you can log in as many times as you wanton different apps and computers to the AIM servers), but is essentially to make sure you are connecting to who you invited.
This SIP Process is very much like an old fashioned operator call in that you call the operator they call the operator at the other end who calls the Buddy, he answers his operator who confirms he is willing to chat... etc.
As with a telephone call you want to make sure you are talking to the right person.
Like a telephone iChat has to be in "one place" in relation to the internet.
Unlike a corner plot house it can not have one "number" in one street and another in the side road (even local authorities and postal service ignore this).
The process in other IM apps is mixed.
Skype spreads it's connection over as many hosts as will accept them meaning your call could be using 30 or 40 other end users to spread that load.
Of course this also increases the ports in use giving you less security overall.
Some do seem "better" at ignoring secondary connections the way Web Browsers do.
10:33 PM Tuesday; June 30, 2009