IChat Auto-Accept Screen Share

I'm trying control my mac remotely. There is a script that worked prior to 10.6
Is there a new script or workaround to make this possible?

Did you set it for Specific Buddies and not list them ?
9:41 PM Friday; September 17, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Similar Messages

IChat Auto Accept Chats?

Can i get iChat to auto accept calls from only me, which ever remote username i am using? i see it auto accepts but only me. i am the only one i nthe buddy list so is that a way?
is it safe that if i dont allow anyone else to join my buddy list then its safe to auto accept as its only me thats calling? Its the screen sharing over iChat i'm interested in so dont want to be allowing random chats to take over my machine...

HI,
One setting in the Preferences > General section is about the Status Message getting set to Display an Away Status when your "Away"/Inactive from the computer.
iChat uses what is called the Idle time (It makes your Status go Amber when seen by other people)
This happens 10 mins after the last Keyboard or mouse/Trackpad entry/movement.
It does help to set this so It does not change the status.
Next go to System Preferences > Energy Saver (Second row) and set the Computer Not to Sleep (You can Sleep the Display)
7:41 PM Thursday; March 29, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Ichat auto accept for file transfer? way to combine buddy lists?

1) on the new leopard ichat, is there an auto-accept mode for file transfers so that anyone on my buddy list can automatically send me files?
2) i have a google chat and aim accounts running. they run on separate buddy lists. is there a way to combine them to only have one buddy list window?

You can actually. Go to iChat > Preferences > Alerts, select "Incoming File Transfers" from the pull-down menu, check "Run AppleScript", select "Auto Accept.applescript". Your file transfers will be accepted by default

IChat auto accepting audio/video invitations

When I'm logged into iChat and my camera and microphone are enabled, my iChat automatically accepts any invitation for an audio or video chat from users not on my local network. I can't find any information about this problem happening to anyone else, nor how to fix it. It's scary to know that people can start video chatting with me, and see me, without my knowledge or permission. Please help!!

Hi
Has this ever been done on your mac http://www.macosxhints.com/article.php?story=20050512152831112
Or has this been installed http://www.macupdate.com/info.php/id/20684/itwist-%27n-go
Tony

Auto Accept with Screen Sharing with Yosemite Messages App

I take care of many of my family and friend's Macs and I'm really excited that screen sharing with 10.10 Yosemite through iMessage. I'm wondering if anyone know of a way to enrol their Macs into auto-accepting me to control the screen without the need for them to accept it. I know there was a way to do this back in the days of iChat.

Hi,
In Any Finder window use the Go Menu whilst holding down the ALT key.
Select the Library that appears and the navigate to Application Scripts/com.apple.iChat
Double click the Auto Accept item to open in in the Script Editor (formerly AppleScript Editor)
You will note the Text section at the top is commented out by being between (* and then the text and then *) the stars and parentheses.
Later a single line is also commented out with a # symbol
In iChat the section for Auto Accepting Screen Sharing used to be commentated out (originally it was not even there)
You might decide to comment out the other lines leaving just the bits you want. (or Copy the AppleScript and alter the copy).
Then you can go to Messages > Preferences > General Section and select the AppleScript as the Messages Received item.
NOTE
I have had issue myself with the AppleScripts as they stand in Yosemite.
I have tried several of those that are Included and some that I have collected from iChat and all return and error messages about timing out at present.
Others have reported the same in various Threads here at the Apple Support Communities.
At present there does not seem to be a work around.
9:07 pm Tuesday; February 24, 2015
 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Automatically accept screen sharing from specific user ???

My mother is a newbie mac user. To be honest, she's a newbie computer user - full stop. She did inherit my PC laptop when I switched, but within a week she had crashed it. The mac she has is still running. (And guess who got it for her. I'm a good daughter.)
Anyway - her G4 Powermac is running Leopard like a dream. In fact it is much faster now than before. Still, she has a few issues. Like the other day, she couldn't get music through her speakers and I'm abroad at the time.
I asked her to accept a screen share, she did. I fixed the speaker issue and closed the screen share. She is happy as larry. But that got me thinking. Is it possible to automatically accept screen share from certain users? That would be a great help if that would be possible.
Thanks in advance.

Musicsites, here is your answer. Just follow the instructions completely and it will work quite well. I have it running and it allows my iMac to automatically answer incoming Screen Sharing requests ONLY from my MacBook.
<http://www.getstonered.com/2007/11/applescript-automatically-accept-ichat.html>
Mike

IChat screen share not working

Hi,
WHen i request a screen share with someone else, it tries to connect and the audio comes up for a couple seconds, then it says the other person stopped it. On the other end it looks like its going to connect with the "sharing screen" bar across the screen then says disconnected. Any ideas???

Of course it is better to start with a log fle from a working session. So I set the bandwith fixed at 1,5 Mbps, and after several attempts I succeeded in catching a logfile of a succesfull remote screen session using the command /Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7 from within Terminal.
iChats port are not open on both sites, because in real world I cannot and don't want to remotely adjust modemconnections before having remote screen running and because i have 2 mac's on my site. So SNATMAP has to do the job and you see a lot of SNATMAP things going on (comparable with STUN) to find out how internal addres/port combination can be reached from the outsite using the principle that when a UDP portmapping is being used for outsite traffic, it can also be used for incoming UDP traffic.
As by buddy has VMWare installed, 2 extra local interfaces and thus local addresses are involved, resulting in more ip address/port combinations to be tested.
As you can see from the logging, iChat's remote screen does use port 16402 on both Mac's, and due to UDP portmapping not on the public ip addresses of the router.
Next thing i will test is to forward iChat ports on my local modem, however using Game/ Aplication sharing I didnot success yet. 1e idea is that Speedtouch ignores Games/Application with higher portnumbers (forwarding 6402 succeeded, 16402 not. Otherwise i have to go for the Command Line Interface.
[MacBook-Pro:~] rob% /Users/rob/Desktop/ichatdebug ; exit;
232314.323609 ER_AddFilter (0): Adding [[email protected]]->[0]
232314.323903 setLocalUserName: [email protected]
232314.326836 Creating a port mapping from 54483 to 16402...
232314.329812 Default video size is (640 x 480)
232314.331505 H264: (640 x 480) @ 20 fps
232314.333836 H264: (320 x 240) @ 30 fps
232314.335020 H264: (160 x 120) @ 30 fps
232314.336284 H263: (352 x 288) @ 30 fps
232314.337538 H263: (176 x 144) @ 30 fps
232314.337890 ######################################
232314.338016 # SoundDec_Create(81536 --> 393219) #
232314.338165 ######################################
232314.342480 Leaving SoundDec_Create
232314.342693 ### NEW STATE: to: VC_INIT, from: VC_INVALID
232314.342789 ### NEW STATE: to: VC_IDLE, from: VC_INIT
232314.342813 ++++++++ confStatusMapRemoveAll
232314.342827 ( ) -- mapUserIDToSecurityInfo cleared --
232314.342885 NATTraversal created
232314.343047 Bandwidth based on QT prefs = 1500
232314.351050 Selected microphone is the null device microphone.
232314.351289 vcCapabilitiesOfCPU returns: 0x00000fff
232314.351321 VCCapAudio
232314.351332 VCCapVideo
232314.351363 VCCapMultiAudio
232314.351373 VCCapMultiVideo
232314.351379 VCCapMultiAudioHost
232314.351412 VCCapMultiVideoHost
232314.351423 VCCapRDClient
232314.351449 VCCapRDServer
232314.351458 VCCapRecordAudio
232314.351463 VCCapRecordVideo
232314.351469 VCCapAuxVideoSend
232314.351474 VCCapAuxVideoRecv
232314.351725 BWD: GotBandwidth: 221052/394013 (up/down) @[173.0.0.10:0.255.255.255]
232314.351788 BWD bandwidth: 221 kbits up, 394 kbits down.
232314.351840 videoNetworkCapable: 1 -- 2 max participants.
232314.351877 audioNetworkCapable: 1 -- 9 max participants.
232314.351933 Supports PCMU wideband for audio: 1 / video: 0
232314.351990 vcCapabilitiesOfNetwork returns: 0x00000bdf
232314.352020 VCCapAudio
232314.352029 VCCapVideo
232314.352034 VCCapMultiAudio
232314.352067 VCCapMultiVideo
232314.352077 VCCapMultiAudioHost
232314.352103 VCCapRDClient
232314.352111 VCCapRDServer
232314.352117 VCCapRecordAudio
232314.352123 VCCapRecordVideo
232314.352156 VCCapAuxVideoRecv
232314.352165 vcCapabilities returns: 0x00000bdf
232314.352193 VCCapAudio
232314.352202 VCCapVideo
232314.352207 VCCapMultiAudio
232314.352213 VCCapMultiVideo
232314.352219 VCCapMultiAudioHost
232314.352225 VCCapRDClient
232314.352230 VCCapRDServer
232314.352236 VCCapRecordAudio
232314.352241 VCCapRecordVideo
232314.352247 VCCapAuxVideoRecv
232314.353296 Found 1 cameras:
232314.353327 Built-in iSight - 18446744073663414272
232314.357103 Microphone devices:
232314.357187 Internal microphone
232314.357333 Line In
232314.357411 Selected microphone is the null device microphone.
232314.357550 vcCapabilitiesOfCPU returns: 0x00000fff
232314.359585 VCCapAudio
232314.369834 VCCapVideo
232314.369842 VCCapMultiAudio
232314.369848 VCCapMultiVideo
232314.369853 VCCapMultiAudioHost
232314.369859 VCCapMultiVideoHost
232314.369865 VCCapRDClient
232314.369870 VCCapRDServer
232314.369876 VCCapRecordAudio
232314.369882 VCCapRecordVideo
232314.369887 VCCapAuxVideoSend
232314.369893 VCCapAuxVideoRecv
232314.370134 BWD: GotBandwidth: 221052/394013 (up/down) @[173.0.0.10:0.255.255.255]
232314.370171 BWD bandwidth: 221 kbits up, 394 kbits down.
232314.370180 videoNetworkCapable: 1 -- 2 max participants.
232314.370187 audioNetworkCapable: 1 -- 9 max participants.
232314.370223 Supports PCMU wideband for audio: 1 / video: 0
232314.370448 vcCapabilitiesOfNetwork returns: 0x00000bdf
232314.370461 VCCapAudio
232314.370467 VCCapVideo
232314.370473 VCCapMultiAudio
232314.370479 VCCapMultiVideo
232314.370485 VCCapMultiAudioHost
232314.370490 VCCapRDClient
232314.370496 VCCapRDServer
232314.370502 VCCapRecordAudio
232314.370508 VCCapRecordVideo
232314.370513 VCCapAuxVideoRecv
232314.370519 vcCapabilities returns: 0x00000bdf
232314.370526 VCCapAudio
232314.370531 VCCapVideo
232314.370537 VCCapMultiAudio
232314.370542 VCCapMultiVideo
232314.370548 VCCapMultiAudioHost
232314.370554 VCCapRDClient
232314.370559 VCCapRDServer
232314.370565 VCCapRecordAudio
232314.370570 VCCapRecordVideo
232314.370576 VCCapAuxVideoRecv
232314.370728 Found 1 cameras:
232314.370803 Built-in iSight - 18446744073663414272
232314.371151 selectCameraByGUID: 18446744073663414272 returned 1
232314.374920 Microphone devices:
232314.375031 Internal microphone
232314.375137 Line In
232314.375188 Selected mic: Built-in Microphone / imic
232314.378512 Selected microphone is Internal microphone.
232314.690739 SNATMAP Configuration: snatmap.mac.com:5678
232314.881515 Comm reporting flags: 00000102
232315.053347 CommNAT result:
External IP: a.b.c.d
External ip is the outsite internet address of the modem
External Ports: 42553, 42553, 42553
External ports are the outsite ports of the modem
CNAT_BADTEST ....... 0
CNAT_ISFULLCONE .... 1
CNAT_ISPAT ......... 0
CNAT_ISPATHOST ..... 0
CNAT_TRYPRESERVE ... 0
CNAT_PATINORDER .... 0
CNAT_BLOCKIP ....... 0
CNAT_BLOCKPORT ..... 0
CNAT_LOOPBACK ...... 1
232315.105100 Found 1 cameras:
232315.105166 Built-in iSight - 18446744073663414272
232315.105210 selectedCamera GUID returned Built-in iSight
232315.109244 Microphone devices:
232315.109393 Internal microphone
232315.109515 Line In
232315.109624 Selected mic: Built-in Microphone / imic
232315.131113 Selected microphone is Internal microphone.
232315.132039 Found 1 cameras:
232315.132082 Built-in iSight - 18446744073663414272
232315.132115 selectedCamera GUID returned Built-in iSight
232315.136026 Microphone devices:
232315.136137 Internal microphone
232315.136260 Line In
232315.136338 Selected mic: Built-in Microphone / imic
232315.157190 Selected microphone is Internal microphone.
232317.828689 in callback
232317.828719 -sdRef 0x14786ec0 ?
232317.828738 -flags = 00000000
232317.828752 -IFIndex 0 ?
232317.828764 -errorCode == 00000000
232317.828785 -publicAddr == 0.0.0.0
232317.828798 -proto == 16
232317.828809 -privPort == 16402
232317.828821 -publPort == 0
232317.828833 -ttl == 0
232322.824973 VTPRecvProc thread(-1336614912) started...
232322.825410 SIPManager init with protocol: 0.
232322.825777 1 interfaces found.
232322.826005 Start listening on 10.0.0.173:16402(en1) sock 100
10.0.0.173:16402 is the ip address and port of my mac, so it using the iChat port
232322.826032 1 valid interfaces found.
232322.826087 TPListen on port 16402
232322.826180 Transport(UDP) Thread start...
232322.892004 vcCapabilitiesOfCPU returns: 0x00000fff
232322.892029 VCCapAudio
232322.892036 VCCapVideo
232322.892041 VCCapMultiAudio
232322.892047 VCCapMultiVideo
232322.892053 VCCapMultiAudioHost
232322.892060 VCCapMultiVideoHost
232322.892066 VCCapRDClient
232322.892072 VCCapRDServer
232322.892077 VCCapRecordAudio
232322.892083 VCCapRecordVideo
232322.892089 VCCapAuxVideoSend
232322.892095 VCCapAuxVideoRecv
232322.892227 BWD: GotBandwidth: 221052/394013 (up/down) @[173.0.0.10:0.255.255.255]
232322.892248 BWD bandwidth: 221 kbits up, 394 kbits down.
232322.892256 videoNetworkCapable: 1 -- 2 max participants.
232322.892262 audioNetworkCapable: 1 -- 9 max participants.
232322.892268 Supports PCMU wideband for audio: 1 / video: 0
232322.892292 vcCapabilitiesOfNetwork returns: 0x00000bdf
232322.892300 VCCapAudio
232322.892305 VCCapVideo
232322.892311 VCCapMultiAudio
232322.892317 VCCapMultiVideo
232322.892322 VCCapMultiAudioHost
232322.892328 VCCapRDClient
232322.892334 VCCapRDServer
232322.892339 VCCapRecordAudio
232322.892345 VCCapRecordVideo
232322.892351 VCCapAuxVideoRecv
232322.892356 vcCapabilities returns: 0x00000bdf
232322.892362 VCCapAudio
232322.892368 VCCapVideo
232322.892373 VCCapMultiAudio
232322.892379 VCCapMultiVideo
232322.892385 VCCapMultiAudioHost
232322.892390 VCCapRDClient
232322.892396 VCCapRDServer
232322.892401 VCCapRecordAudio
232322.892407 VCCapRecordVideo
232322.892413 VCCapAuxVideoRecv
232322.893662 VCDelegate conforms to VideoConferenceDelegate protocol.
232322.893686 ER_AddFilter (1): Adding [[email protected]]->[0]
232322.893701 setLocalUserName: [email protected]
232322.893719 ( ) setValidatedIdentity: [00000000]
232322.960684 1 interfaces found.
232322.960734 Start listening on 10.0.0.173:49214
it selects a random port
232322.960743 1 valid interfaces found.
232322.960777 candidate collection start : 9.309272
232322.960829 SNATMAP server [17.250.248.149:5678]
232322.960890 Found 1 cameras:
232322.960915 Built-in iSight - 18446744073663414272
232322.960959 selectedCamera GUID returned Built-in iSight
232322.960504 candidate collection start : 9.308984
232322.961044 SNATMAP server [17.250.248.149:5678]
232322.961097 sent SNATMAP request for [10.0.0.173:16402]
request how 10.0.0.173:16402 looks on the outsite on the public internet
232322.961211 sent SNATMAP request for [10.0.0.173:49214]
request how 10.0.0.173:49214 looks on the outsite on the public internet
232322.961264 VCChannelRecvProc start...
232322.964830 Microphone devices:
232322.964904 Internal microphone
232322.964970 Line In
232322.965011 Selected mic: Built-in Microphone / imic
232322.981400 Selected microphone is Internal microphone.
232323.133001 SNATMAP mapping [a.b.c.d:42744]
232323.133068 candidate collection done : 9.481563
232323.133107 add LOCAL candidate [10.0.0.173:49214]
232323.133133 add SNATMAP candidate [a.b.c.d:42744]
10.0.0.173:49214 might match a.b.c.d:42744
232323.133729 Adding [en1] to DNSSD ip port list:[0.0.0.0:54483]
selects another random port
232323.133798 upnp mapping is invalid [0.0.0.0:54483], use snatmap IP.
232323.133827 add UPnP candidate [a.b.c.d:54483]
232323.134891 SNATMAP mapping [a.b.c.d:42454]
232323.134913 candidate collection done : 9.483408
232323.134935 add LOCAL candidate [10.0.0.173:16402]
232323.134954 add SNATMAP candidate [a.b.c.d:42454]
232323.135101 Adding [en1] to DNSSD ip port list:[0.0.0.0:54483]
232323.135125 upnp mapping is invalid [0.0.0.0:54483], use snatmap IP.
232323.135143 add UPnP candidate [a.b.c.d:54483]
232323.135408 VCConnectionData for call id: 1 returns 0x17d531f0
232328.223281 ICEStartConnectivityCheck(id[local:1 remote:1] count[local:3 remote:3] candidate[local:0x17D45660 remote:0x17DAAF10] pair[0x011B0A00]
232328.223350 connectivity check thread start...(-1334484992)
232328.223366 join connectivity check thread(-1334484992)...
232328.223412 *** Insert conn check events ***
start checking which interface/ip/port combinations are end to end connected
the remote end got more then one local addresses which makes it complex,
address 192.168.1.150 on airport
address 192.168.71.1 on virtal machine
192.168.71.1 on virtual machine
232328.223435 event 10.0.0.173:49214->192.168.1.150:49213 expires 14.621923
232328.223457 event 10.0.0.173:49214->w.x.y.z:49388 expires 14.671923
232328.223474 event a.b.c.d:42744->192.168.1.150:49213 expires 14.721923
232328.223492 event 10.0.0.173:49214->w.x.y.z:53646 expires 14.771923
232328.223509 event a.b.c.d:54483->192.168.1.150:49213 expires 14.821923
232328.223526 event a.b.c.d:42744->w.x.y.z:49388 expires 14.871923
232328.223543 event a.b.c.d:42744->w.x.y.z:53646 expires 14.921923
232328.223560 event a.b.c.d:54483->w.x.y.z:49388 expires 14.971923
232328.223576 event a.b.c.d:54483->w.x.y.z:53646 expires 15.021923
232328.223884 vcCapabilitiesOfCPU returns: 0x00000fff
232328.223904 VCCapAudio
232328.223916 VCCapVideo
232328.223926 VCCapMultiAudio
232328.223935 VCCapMultiVideo
232328.223945 VCCapMultiAudioHost
232328.223954 VCCapMultiVideoHost
232328.223963 VCCapRDClient
232328.223973 VCCapRDServer
232328.223982 VCCapRecordAudio
232328.223992 VCCapRecordVideo
232328.224001 VCCapAuxVideoSend
232328.224010 VCCapAuxVideoRecv
232328.224206 BWD: GotBandwidth: 221052/394013 (up/down) @[173.0.0.10:0.255.255.255]
232328.224242 BWD bandwidth: 221 kbits up, 394 kbits down.
232328.224255 videoNetworkCapable: 1 -- 2 max participants.
232328.224265 audioNetworkCapable: 1 -- 9 max participants.
232328.224276 Supports PCMU wideband for audio: 1 / video: 0
232328.224313 vcCapabilitiesOfNetwork returns: 0x00000bdf
232328.224327 VCCapAudio
232328.224336 VCCapVideo
232328.224346 VCCapMultiAudio
232328.224355 VCCapMultiVideo
232328.224365 VCCapMultiAudioHost
232328.224374 VCCapRDClient
232328.224384 VCCapRDServer
232328.224393 VCCapRecordAudio
232328.224403 VCCapRecordVideo
232328.224413 VCCapAuxVideoRecv
232328.224422 vcCapabilities returns: 0x00000bdf
232328.224432 VCCapAudio
232328.224442 VCCapVideo
232328.224451 VCCapMultiAudio
232328.224461 VCCapMultiVideo
232328.224470 VCCapMultiAudioHost
232328.224480 VCCapRDClient
232328.224489 VCCapRDServer
232328.224499 VCCapRecordAudio
232328.224508 VCCapRecordVideo
232328.224518 VCCapAuxVideoRecv
232328.226505 prepareConnection - remote VCConnectionData: 01092600, local VCConnectionData: 011a5000
232328.226798 ICEStartConnectivityCheck(id[local:1 remote:2] count[local:3 remote:5] candidate[local:0x17D6AAC0 remote:0x011B4C00] pair[0x011BC800]
232328.226828 connectivity check thread start...(-1332887552)
232328.227021 *** Insert conn check events ***
232328.227037 event 10.0.0.173:16402->192.168.71.1:16402 expires 14.625528
232328.227050 event a.b.c.d:42454->192.168.71.1:16402 expires 14.675528
232328.227060 event 10.0.0.173:16402->192.168.1.150:16402 expires 14.725528
232328.227070 event a.b.c.d:54483->192.168.71.1:16402 expires 14.775528
232328.227080 event 10.0.0.173:16402->192.168.177.1:16402 expires 14.825528
232328.227089 event 10.0.0.173:16402->w.x.y.z:49387 expires 14.875528
232328.227099 event 10.0.0.173:16402->w.x.y.z:53646 expires 14.925528
232328.227109 event a.b.c.d:42454->192.168.1.150:16402 expires 14.975528
232328.227119 event a.b.c.d:54483->192.168.1.150:16402 expires 15.025528
232328.227145 event a.b.c.d:42454->192.168.177.1:16402 expires 15.075528
232328.227155 event a.b.c.d:42454->w.x.y.z:49387 expires 15.125528
232328.227165 event a.b.c.d:42454->w.x.y.z:53646 expires 15.175528
232328.227175 event a.b.c.d:54483->192.168.177.1:16402 expires 15.225528
232328.227185 event a.b.c.d:54483->w.x.y.z:49387 expires 15.275528
232328.227194 event a.b.c.d:54483->w.x.y.z:53646 expires 15.325528
232328.229577 Invoke delegate method vcc:initiateConferenceStartedForParty:([email protected])
232328.229606 ### NEW STATE: to: VC_SIGNALING, from: VC_IDLE
232328.229617 initiateConferenceCallUsingConnectionDataWithErrorInfoToUser - start
232328.229634 Callee connection data 917 bytes. Caller connection data 621 bytes.
232328.229652 ( )( )( ) ---- <nil> valid returned 0
232328.229666 =========== OpenPorts!
232328.229678 Audio only conference.
232328.229728 RTP/RTCP ports for PayloadType 0 are 16402 and 16402
232328.229834 RTP vfd (102) accepts pkt (0008)
232328.229844 RTP vfd (103) accepts pkt (0020)
232328.233983 selectedCamera GUID returned Built-in iSight
232328.234589 * Caller SDP *
232328.234852 v=0
o=rob 0 0 IN %RTP-IP-AF% %RTP-IP%
[email protected]
c=IN %RTP-IP-AF% %RTP-IP%
b=AS:2147483647
t=0 0
a=hwi:17412:2:2400
a=iChatEncryption:NO
m=audio %ARTP-PORT% RTP/AVP 110 121 12 3 0
a=rtcp:%ARTCP-PORT%
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:2041791258
m=video %VRTP-PORT% RTP/AVP 123 126 34
a=rtcp:%VRTCP-PORT%
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO %ARTCP-PORT% VIDEO %VRTCP-PORT%
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:0
232328.234871 <<<<<<<<<< Conference initiation API version 2 >>>>>>>>>
232328.235464 join connectivity check thread(-1332887552)...
232328.371845 *** event (10.0.0.173:49214->192.168.1.150:49213) fired ***
232328.372146 BINDING_REQUEST to 192.168.1.150:49213 from 10.0.0.173:49214
232328.372190 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.376309 *** event (10.0.0.173:16402->192.168.71.1:16402) fired ***
232328.376515 BINDING_REQUEST to 192.168.71.1:16402 from 10.0.0.173:16402
232328.376532 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.520369 *** event (10.0.0.173:49214->w.x.y.z:49388) fired ***
232328.520657 BINDING_REQUEST to w.x.y.z:49388 from 10.0.0.173:49214
232328.520683 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.525711 *** event (a.b.c.d:42454->192.168.71.1:16402) fired ***
232328.525919 BINDING_REQUEST to 192.168.71.1:16402 from a.b.c.d:42454
232328.525945 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.659954 *** BINDING_REQUEST from (w.x.y.z:49389) ***
232328.659974 OLD STATE(TESTING)->NEW STATE(TESTING)
232328.660057 BINDING_RESPONSE to (w.x.y.z:49389)
232328.660065 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232328.660073 new remote address(w.x.y.z:49389)
232328.660089 created candidate (type = 6)
232328.660097 *** Insert conn check events ***
232328.660109 event a.b.c.d:42454->w.x.y.z:49389 expires 15.375528
232328.660119 RCCount=6 CPCount=16
232328.660130 *** event (10.0.0.173:16402->192.168.1.150:16402) fired ***
232328.660183 BINDING_REQUEST to 192.168.1.150:16402 from 10.0.0.173:16402
232328.660191 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.668740 *** event (a.b.c.d:42744->192.168.1.150:49213) fired ***
232328.668782 BINDING_REQUEST to 192.168.1.150:49213 from a.b.c.d:42744
232328.668820 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.807277 *** BINDING_REQUEST from (w.x.y.z:49390) ***
232328.807314 OLD STATE(TESTING)->NEW STATE(TESTING)
232328.807400 BINDING_RESPONSE to (w.x.y.z:49390)
232328.807415 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232328.807430 new remote address(w.x.y.z:49390)
232328.807446 created candidate (type = 6)
232328.807462 *** Insert conn check events ***
232328.807482 event a.b.c.d:42744->w.x.y.z:49390 expires 15.071923
232328.807500 RCCount=4 CPCount=10
232328.807522 *** event (10.0.0.173:49214->w.x.y.z:53646) fired ***
232328.807585 BINDING_REQUEST to w.x.y.z:53646 from 10.0.0.173:49214
232328.807601 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.809357 *** event (a.b.c.d:54483->192.168.71.1:16402) fired ***
232328.809529 BINDING_REQUEST to 192.168.71.1:16402 from a.b.c.d:54483
232328.809555 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.955862 *** event (a.b.c.d:54483->192.168.1.150:49213) fired ***
232328.956293 BINDING_REQUEST to 192.168.1.150:49213 from a.b.c.d:54483
232328.956345 OLD STATE(WAITING)->NEW STATE(TESTING)
232328.958788 *** event (10.0.0.173:16402->192.168.177.1:16402) fired ***
232328.959037 BINDING_REQUEST to 192.168.177.1:16402 from 10.0.0.173:16402
232328.959101 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.104599 *** event (a.b.c.d:42744->w.x.y.z:49388) fired ***
232329.105030 BINDING_REQUEST to w.x.y.z:49388 from a.b.c.d:42744
232329.105076 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.108284 *** event (10.0.0.173:16402->w.x.y.z:49387) fired ***
232329.108538 BINDING_REQUEST to w.x.y.z:49387 from 10.0.0.173:16402
232329.108602 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.126053 *** BINDING_REQUEST from (w.x.y.z:49390) ***
232329.126109 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.126300 BINDING_RESPONSE to (w.x.y.z:49390)
232329.126316 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.126338 *** event (a.b.c.d:42744->w.x.y.z:53646) fired ***
232329.126410 BINDING_REQUEST to w.x.y.z:53646 from a.b.c.d:42744
232329.126425 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.146684 *** BINDING_REQUEST from (w.x.y.z:49390) ***
232329.146734 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.146842 BINDING_RESPONSE to (w.x.y.z:49390)
232329.146854 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.146881 *** event (a.b.c.d:54483->w.x.y.z:49388) fired ***
232329.146920 BINDING_REQUEST to w.x.y.z:49388 from a.b.c.d:54483
232329.146964 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.257740 *** event (10.0.0.173:16402->w.x.y.z:53646) fired ***
232329.258002 BINDING_REQUEST to w.x.y.z:53646 from 10.0.0.173:16402
232329.258033 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.295116 *** event (a.b.c.d:54483->w.x.y.z:53646) fired ***
232329.295471 BINDING_REQUEST to w.x.y.z:53646 from a.b.c.d:54483
232329.295487 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.407280 *** event (a.b.c.d:42454->192.168.1.150:16402) fired ***
232329.408097 BINDING_REQUEST to 192.168.1.150:16402 from a.b.c.d:42454
232329.408133 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.427067 *** BINDING_REQUEST from (w.x.y.z:49389) ***
232329.427116 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.427260 BINDING_RESPONSE to (w.x.y.z:49389)
232329.427528 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.427575 *** event (a.b.c.d:54483->192.168.1.150:16402) fired ***
232329.427719 BINDING_REQUEST to 192.168.1.150:16402 from a.b.c.d:54483
232329.427743 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.443609 *** event (a.b.c.d:42744->w.x.y.z:49390) fired ***
232329.444137 BINDING_REQUEST to w.x.y.z:49390 from a.b.c.d:42744
232329.444166 OLD STATE(SEND_VALID)->NEW STATE(SEND_VALID)
232329.463903 *** BINDING_RESPONSE from (w.x.y.z:49390) ***
232329.463955 OLD STATE(SEND_VALID)->NEW STATE(VALID)
232329.463980 Add result(id:1 proto:5): a.b.c.d:42744-w.x.y.z:49390
232329.464097 connectivity check thread(-1334484992) end...(00000000).
232329.464131 use result (id=1,proto=5): local=10.0.0.173:49214 remote=192.168.1.150:49213 src=a.b.c.d:42744 dst=w.x.y.z:49390
232329.464223 VCChannelRecvProc end(00000000)...
from all the ip/port combinations local=10.0.0.173:49214 remote=192.168.1.150:49213 src=a.b.c.d:42744 dst=w.x.y.z:49390 is OK
so my mac ip/port 10.0.0.173:49214 can be reached from internet by src=a.b.c.d:42744
my budies mac ip/port 192.168.1.150:49213 can be reached fro the internet by dst=w.x.y.z:49390
232329.576937 *** event (a.b.c.d:42454->192.168.177.1:16402) fired ***
232329.577200 BINDING_REQUEST to 192.168.177.1:16402 from a.b.c.d:42454
232329.577259 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.597178 *** BINDING_REQUEST from (w.x.y.z:49389) ***
232329.597213 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.597392 BINDING_RESPONSE to (w.x.y.z:49389)
232329.597411 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.597435 *** event (a.b.c.d:42454->w.x.y.z:49387) fired ***
232329.597509 BINDING_REQUEST to w.x.y.z:49387 from a.b.c.d:42454
232329.597525 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.618579 *** BINDING_REQUEST from (w.x.y.z:49389) ***
232329.618604 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.618671 BINDING_RESPONSE to (w.x.y.z:49389)
232329.618681 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.618696 *** event (a.b.c.d:42454->w.x.y.z:53646) fired ***
232329.618728 BINDING_REQUEST to w.x.y.z:53646 from a.b.c.d:42454
232329.618739 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.638578 *** BINDING_REQUEST from (w.x.y.z:49389) ***
232329.638614 OLD STATE(TESTING)->NEW STATE(TESTING)
232329.638800 BINDING_RESPONSE to (w.x.y.z:49389)
232329.638819 OLD STATE(TESTING)->NEW STATE(SEND_VALID)
232329.638841 *** event (a.b.c.d:54483->192.168.177.1:16402) fired ***
232329.638986 BINDING_REQUEST to 192.168.177.1:16402 from a.b.c.d:54483
232329.639180 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.788416 *** event (a.b.c.d:54483->w.x.y.z:49387) fired ***
232329.788662 BINDING_REQUEST to w.x.y.z:49387 from a.b.c.d:54483
232329.788706 OLD STATE(WAITING)->NEW STATE(TESTING)
232329.937956 *** event (a.b.c.d:54483->w.x.y.z:53646) fired ***
232329.938195 BINDING_REQUEST to w.x.y.z:53646 from a.b.c.d:54483
232329.938239 OLD STATE(WAITING)->NEW STATE(TESTING)
232330.087487 *** event (a.b.c.d:42454->w.x.y.z:49389) fired ***
232330.087728 BINDING_REQUEST to w.x.y.z:49389 from a.b.c.d:42454
232330.087770 OLD STATE(SEND_VALID)->NEW STATE(SEND_VALID)
232330.108475 *** BINDING_RESPONSE from (w.x.y.z:49389) ***
232330.108510 OLD STATE(SEND_VALID)->NEW STATE(VALID)
232330.108533 Add result(id:1 proto:0): a.b.c.d:42454-w.x.y.z:49389
232330.108658 connectivity check thread(-1332887552) end...(00000000).
232330.108692 use result (id=1,proto=0): local=10.0.0.173:16402 remote=192.168.71.1:16402 src=a.b.c.d:42454 dst=w.x.y.z:49389
ALSO from all the ip/port combinations local=10.0.0.173:16402 remote=192.168.71.1:16402 src=a.b.c.d:42454 dst=w.x.y.z:49389 is OK
232330.108714 SIPConnect start...
232330.108748 ER_AddFilter (2): Adding [[email protected]]->[u0]
232330.108781 ER_AddFilter (3): Adding [10.0.0.173]->[lip]
232330.108799 ER_AddFilter (4): Adding [10-0-0-173]->[lip]
232330.108817 ER_AddFilter (5): Adding [192.168.71.1]->[rip]
232330.108832 ER_AddFilter (6): Adding [192-168-71-1]->[rip]
232330.108850 ER_AddFilter (7): Adding [a.b.c.d]->[sip]
232330.108865 ER_AddFilter (8): Adding [a-b-c-d]->[sip]
232330.109078 TAInviteClientProc Thread start...
232330.109173 ( )( )( )( )( ) TP IS BINARY? (0)
232330.109425 Send to w.x.y.z:49389 [INVITE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK4aec1ff55bcddc90
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
The ip/port combination with iChat ports 16402 is used on both ends
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 INVITE
Contact: <sip:[email protected]:42454>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 402
v=0
o=rob 0 0 IN IP4 a.b.c.d
[email protected]
c=IN IP4 a.b.c.d
b=AS:2147483647
t=0 0
a=hwi:17412:2:2400
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 42454 RTP/AVP 110 121 12 3 0
a=rtcp:42454
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:2041791258
232330.151861 [[SIP/2.0 100 Trying
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK4aec1ff55bcddc90
To: "[email protected]" <sip:[email protected]:16402>
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 INVITE
User-Agent: Viceroy 1.3
Content-Length: 0
]] from w.x.y.z:49389
232330.152045 Dialog(CREATED) Match(STATUS) [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416]
232330.152116 Dialog(CREATED) Match(STATUS) [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416]
232330.152178 ##### (1)Trying...
232330.152790 VCSendNotificationProc: name = VCInformation, data = Trying
232330.152898 [[SIP/2.0 180 Ringing
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK4aec1ff55bcddc90
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 INVITE
Contact: <sip:[email protected]:49389>
User-Agent: Viceroy 1.3
Content-Length: 0
]] from w.x.y.z:49389
232330.152964 Dialog(CREATED) Match(STATUS) [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416]
232330.153017 Dialog(CREATED) Match(STATUS) [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416]
232330.153082 ##### (1)Ringing...
232330.153402 VCSendNotificationProc: name = VCInformation, data = Ringing
232330.159914 [[SIP/2.0 200 OK
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK4aec1ff55bcddc90
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 INVITE
Contact: <sip:[email protected]:49389>
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 265
v=0
o=steve 0 0 IN IP4 w.x.y.z
[email protected]
c=IN IP4 w.x.y.z
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=bandwidthDetection:YES
a=iChatEncryption:NO
m=audio 49389 RTP/AVP 110
a=rtcp:49389
a=rtpmap:110 X-AAC_LD/22050
a=rtpID:2293062722
]] from w.x.y.z:49389
232330.160027 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232330.160109 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232330.160176 TAInviteClientProc Thread end(0)...
232330.160275 ( )( )( )( )( ) TP IS BINARY? (0)
232330.160306 Send to w.x.y.z:49389 [ACK sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK10050bf92bb06081
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 ACK
User-Agent: Viceroy 1.3
Content-Length: 0
232330.160451 Start sending heartbeat from 10.0.0.173:16402 to w.x.y.z:49389
232330.160492 SIPConnect stop(0)...
232330.160592 SIP connect returned 0
232330.160613 Call initiated with callID = 1
232330.161635 Callee User Agent: Viceroy 1.3
232330.161669 * Callee SDP *
232330.161766 Selecting AAC-LD 22.05kHz.
232330.161794 ######################################
232330.161808 # SoundDec_Create(742946 --> 81536) #
232330.161820 ######################################
232330.166394 Leaving SoundDec_Create
232330.166422 Conference_SetPayload: audio = 110, video = 34, for confIndex = 0
232330.166655 v=0
o=steve 0 0 IN IP4 w.x.y.z
[email protected]
c=IN IP4 w.x.y.z
b=AS:2147483647
t=0 0
a=hwi:1056:4:2660
a=bandwidthDetection:YES
a=iChatEncryption:NO
m=audio 49389 RTP/AVP 110
a=rtcp:49389
a=rtpmap:110 X-AAC_LD/22050
a=rtpID:2293062722
232330.166995 RTPSetRemoteSSRC [102/103]: SSRC = 0x88AD5C42(2293062722)
232330.167020 SIPSendMessageAll start...
232330.167071 P2P BWD detection starts for vfd(102) with w.x.y.z:49389
232330.390679 Received the first BWD packet from w.x.y.z:49389
232330.703921 Avg=101190.70, NSDev=2.60%
232330.830048 Avg=872232.80, NSDev=2.48%
232331.132400 Avg=888850.00, NSDev=7.53%
232331.326017 Orig: Upstream = 452.712kbps, Downstream = -800.442kbps
232331.326155 Final: Upstream = 452.712kbps, Downstream = 800.442kbps
232331.326189 P2P BWD detection done for vfd(102)
232331.326401 Detected bandwidth (kbits/s): 452 up, 800 down. (00000000)
2008-08-18 23:23:31.326 iChat[172:11b07] Detected bandwidth (kbits/s): 452 up, 800 down. (00000000)
232331.327811 Add user: [email protected] --> (call id: 1, conf index: 0) to table.
232331.327865 ( )( )( )( )( )( )( )( )( )( )( )( )( )( )( )( ) KEY EXCHANGE 1!
232331.327903 ( )( )( ) ---- [email protected] valid:
232331.327920 ( )( )( ) ---- <nil> valid returned 0
232331.327934 ( )( ) - Overall conference secure: was 0, is 0, count 1
232331.327952 ( )( )( ) ---- @ enabled set to 0
232331.327980 ( )( )( ) ---- @ valid set to 0
232331.328002 Invoke delegate method vcc:securityChanged:
232331.328118 Preparing to send VCInitiateConferenceCompleted
232331.328150 Invoke delegate method vcc:initiateConferenceCompletedForParty:([email protected]) - retcode: 0
232331.332207 vcCapabilitiesOfCPU returns: 0x00000fff
232331.332236 VCCapAudio
232331.332248 VCCapVideo
232331.332258 VCCapMultiAudio
232331.332267 VCCapMultiVideo
232331.332277 VCCapMultiAudioHost
232331.332287 VCCapMultiVideoHost
232331.332296 VCCapRDClient
232331.332306 VCCapRDServer
232331.332316 VCCapRecordAudio
232331.332327 VCCapRecordVideo
232331.332337 VCCapAuxVideoSend
232331.332346 VCCapAuxVideoRecv
232331.332540 BWD: GotBandwidth: 221052/394013 (up/down) @[173.0.0.10:0.255.255.255]
232331.332576 BWD bandwidth: 221 kbits up, 394 kbits down.
232331.332589 videoNetworkCapable: 1 -- 2 max participants.
232331.332600 audioNetworkCapable: 1 -- 9 max participants.
232331.332610 Supports PCMU wideband for audio: 1 / video: 0
232331.332650 vcCapabilitiesOfNetwork returns: 0x00000bdf
232331.332663 VCCapAudio
232331.332674 VCCapVideo
232331.332684 VCCapMultiAudio
232331.332693 VCCapMultiVideo
232331.332703 VCCapMultiAudioHost
232331.332713 VCCapRDClient
232331.332722 VCCapRDServer
232331.332732 VCCapRecordAudio
232331.332742 VCCapRecordVideo
232331.332751 VCCapAuxVideoRecv
232331.332761 vcCapabilities returns: 0x00000bdf
232331.332771 VCCapAudio
232331.332782 VCCapVideo
232331.332791 VCCapMultiAudio
232331.332801 VCCapMultiVideo
232331.332810 VCCapMultiAudioHost
232331.332820 VCCapRDClient
232331.332830 VCCapRDServer
232331.332839 VCCapRecordAudio
232331.332850 VCCapRecordVideo
232331.332859 VCCapAuxVideoRecv
232331.332890 ( )( )( ) ---- {nil} enabled returned 0
232331.333521 Selected microphone is Internal microphone.
232331.333830 Selected microphone is Internal microphone.
232331.334265 Selected microphone is Internal microphone.
232331.334474 MULTIPOINT VC_API: startConferenceWithUserID: [email protected]
232331.334523 MULTIPOINT VC_API: startConferenceWithIndex: 0
232331.334562 Remote User Agent: Viceroy 1.3
232331.334594 upstream_kbits = 452, downstream_kbits = 800
232331.334651 Conference_SetBitrate: 452000
232331.334666 SetBitrate from 0 to 452000
232331.338015 Conference_SetFramerate: 10
232331.338044 Diffusion prefilter disabled
232331.338054 Temporal prefilter disabled
232331.338065 Enabled H264 post processing with mode: 1
232331.338321 Microphone: callback thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
232331.338552 Microphone: null device thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
232331.507802 RTP: recv started(88AD5C42,88AD5C42)
232331.507858 RTPTransport: need to wait for SRTP to init? (0/0)
232331.859180 Speaker: callback thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
232331.859320 Speaker: null device thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17
232331.863156 =================== ActiveCount += 1
232331.863189 SetBitrate from 452000 to 452000
232331.863187 Conference_RecvThread start
232331.865520 =========== StartTransmit!
232331.865536 ######################################
232331.865542 # SoundDec_Create(81536 --> 742946) #
232331.865548 ######################################
232331.880759 Leaving SoundDec_Create
232331.880813 TRANSMIT: w.x.y.z:49389:0 hardwareframe:30 determinedframe: 10 key:-1 determinedbitrate: 452
232331.880846 ### NEW STATE: to: VC_BUSY, from: VC_SIGNALING
232331.880886 AGC = 1
232331.880896 MULTIPOINT VC_API: startConferenceWithUserID: [email protected] returns YES
!!!!!!!!!!!!!!!!!!!!!!!!DATA STARTS HERE REMOTE SCREEN WORKING !!!!!!!!!!!!!!!!!!!!!!!!!!
232331.899517 18.248 jump: 15.2 frames
232332.231957 Entering SPIKE
232332.232465 Leaving SPIKE
232332.242726 18.591 backtrack: -2.0 frames (14415 - 15442, 15255,136,14415)
232332.262975 18.611 silence: 1.0 frames
232332.371732 Entering SPIKE
232332.376195 Leaving SPIKE
232332.384264 18.733 backtrack: -3.0 frames (15951 - 17490, 17315,127,15951)
232332.484788 18.833 silence: 2.0 frames
232332.504760 18.853 silence: 1.0 frames
232332.524727 18.873 -360 warp 512 -> 152
232332.525220 18.874 -360 warp 512 -> 152
232332.525325 18.874 -360 warp 512 -> 152
232332.545114 18.894 -300 skip 320 -> 20
232332.545280 18.894 -320 skip 320 -> 0
232332.545394 18.894 -274 skip 320 -> 46
232337.224342 23.573 silence: 1.0 frames
232337.557761 Entering SPIKE
232337.559545 Leaving SPIKE
232337.583423 23.932 backtrack: -5.0 frames (130639 - 133201, 133155,34,130639)
232337.623150 23.972 silence: 1.0 frames
232337.724208 Entering SPIKE
232337.724475 Leaving SPIKE
232337.922491 24.271 silence: 1.0 frames
232338.002734 24.351 -360 warp 512 -> 152
232338.002961 24.351 -360 warp 512 -> 152
232338.003141 24.352 -300 skip 320 -> 20
232338.022356 24.371 -320 skip 320 -> 0
232338.022509 24.371 -320 skip 320 -> 0
232338.022602 24.371 -200 skip 320 -> 120
232340.681218 27.030 silence: 1.0 frames
232340.802415 27.151 silence: 1.0 frames
232341.384534 27.733 silence: 1.0 frames
232342.821732 29.170 silence: 1.0 frames
232343.684414 30.033 -286 skip 320 -> 34
232346.145433 Entering SPIKE
232346.147096 Leaving SPIKE
232346.163624 32.512 backtrack: -3.0 frames (321615 - 323153, 322735,304,321615)
232346.342369 Entering SPIKE
232346.343541 Leaving SPIKE
232346.403154 32.752 silence: 1.0 frames
232346.542780 32.891 320 dup 320 -> 640
232346.665390 Entering SPIKE
232346.665688 Leaving SPIKE
232346.762355 33.111 silence: 1.0 frames
232346.902314 33.251 silence: 1.0 frames
232348.124035 34.473 silence: 1.0 frames
232348.843019 35.192 silence: 1.0 frames
232349.202130 35.551 -186 skip 320 -> 134
232350.324019 Updating heartbeat from w.x.y.z:49389
232350.329599 [[MESSAGE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP w.x.y.z:49389;branch=z9hG4bK7899611760fc16e0
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=90480416
From: "[email protected]" <sip:[email protected]:16402>;tag=617881761
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.3
Content-Type: text/plain
Content-Length: 4
PING]] from w.x.y.z:49389
232350.329936 Dialog Match(REQUEST): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232350.330076 SIPMessageProc Thread start...
232350.330136 Dialog Match(REQUEST): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232350.330218 TANonInviteServerProc Thread start...
232350.331232 VCSendNotificationProc: name = SIPMessage, data = PING
232350.331267 SIPMessage done.
232350.331315 | | | | --- iBodyLen 0
232350.331408 ( )( )( )( )( ) TP IS BINARY? (0)
232350.331430 Send to w.x.y.z:49389 [SIP/2.0 200 OK
Via: SIP/2.0/UDP w.x.y.z:49389;branch=z9hG4bK7899611760fc16e0
To: "[email protected]" <sip:[email protected]:16402>;tag=90480416
From: "[email protected]" <sip:[email protected]:16402>;tag=617881761
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.3
Content-Length: 0
232350.331589 SIPMessageProc Thread end(200)...
232351.102786 37.451 -187 skip 320 -> 133
232352.826531 SIPSendMessageAll start...
232352.826930 TANonInviteClientProc Thread start...
232352.827042 ( )( )( )( )( ) TP IS BINARY? (0)
232352.827088 Send to w.x.y.z:49389 [MESSAGE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK23daaf2537147c16
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.3
Content-Type: text/plain
Content-Length: 4
PING]
232352.859843 [[SIP/2.0 200 OK
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK23daaf2537147c16
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.3
Content-Length: 0
]] from w.x.y.z:49389
232352.859916 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232352.860137 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232352.860204 SIPSendMessageAll stop(0)...
232353.103040 39.452 silence: 1.0 frames
232353.742084 40.091 silence: 1.0 frames
232353.781901 40.130 -300 skip 320 -> 20
232353.782002 40.130 -253 skip 320 -> 67
232354.103630 40.452 silence: 1.0 frames
232354.544590 40.893 silence: 1.0 frames
232357.762755 44.111 -186 skip 320 -> 134
232357.860351 TANonInviteClientProc Thread end(0)...
232358.625325 44.974 silence: 1.0 frames
232402.003379 48.352 silence: 1.0 frames
232402.321862 48.670 backtrack: -1.0 frames (678479 - 678992, 678608,279,678479)
232402.338076 Entering SPIKE
232402.338209 Leaving SPIKE
232402.441691 48.790 silence: 1.0 frames
232402.561327 48.910 silence: 1.0 frames
232403.703817 50.052 silence: 1.0 frames
232403.823631 50.172 silence: 1.0 frames
232403.923471 50.272 silence: 1.0 frames
232404.043658 Entering SPIKE
232404.045955 Leaving SPIKE
232404.063057 50.412 backtrack: -2.0 frames (715855 - 716881, 716460,306,715855)
232404.242612 50.591 -187 skip 320 -> 133
232404.702022 51.051 silence: 1.0 frames
232405.542301 51.891 -186 skip 320 -> 134
232407.062092 53.411 -186 skip 320 -> 134
232409.161947 55.510 -186 skip 320 -> 134
232409.401506 55.750 silence: 1.0 frames
232411.663480 58.012 silence: 1.0 frames
232412.224780 58.573 -186 skip 320 -> 134
232415.942052 62.291 -186 skip 320 -> 134
232416.544663 62.893 silence: 1.0 frames
232417.363006 63.711 silence: 1.0 frames
232420.326102 Updating heartbeat from w.x.y.z:49389
232420.331354 [[MESSAGE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP w.x.y.z:49389;branch=z9hG4bK47124a6973d60d4e
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=90480416
From: "[email protected]" <sip:[email protected]:16402>;tag=617881761
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.3
Content-Type: text/plain
Content-Length: 4
PING]] from w.x.y.z:49389
232420.331601 Dialog Match(REQUEST): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232420.331817 SIPMessageProc Thread start...
232420.331915 Dialog Match(REQUEST): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232420.332105 TANonInviteServerProc Thread start...
232420.332471 VCSendNotificationProc: name = SIPMessage, data = PING
232420.332512 SIPMessage done.
232420.332540 | | | | --- iBodyLen 0
232420.332731 ( )( )( )( )( ) TP IS BINARY? (0)
232420.332764 Send to w.x.y.z:49389 [SIP/2.0 200 OK
Via: SIP/2.0/UDP w.x.y.z:49389;branch=z9hG4bK47124a6973d60d4e
To: "[email protected]" <sip:[email protected]:16402>;tag=90480416
From: "[email protected]" <sip:[email protected]:16402>;tag=617881761
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.3
Content-Length: 0
232420.332942 SIPMessageProc Thread end(200)...
232420.604802 66.953 -300 skip 320 -> 20
232420.604963 66.953 -197 skip 320 -> 123
232422.331666 TANonInviteServerProc Thread end(0)...
232422.826697 SIPSendMessageAll start...
232422.827021 TANonInviteClientProc Thread start...
232422.827120 ( )( )( )( )( ) TP IS BINARY? (0)
232422.827165 Send to w.x.y.z:49389 [MESSAGE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK0addafcb59113610
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.3
Content-Type: text/plain
Content-Length: 4
PING]
232422.860789 [[SIP/2.0 200 OK
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK0addafcb59113610
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.3
Content-Length: 0
]] from w.x.y.z:49389
232422.860853 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232422.860919 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232422.860970 SIPSendMessageAll stop(0)...
!!!!!!!!!!HERE I STOPPED REMOTE SCREEN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
232425.504261 71.853 silence: 1.0 frames
232426.402536 72.751 silence: 1.0 frames
232427.861074 TANonInviteClientProc Thread end(0)...
232427.963955 74.312 silence: 2.0 frames
232427.984105 74.333 silence: 1.0 frames
232431.862262 78.211 silence: 1.0 frames
232434.081773 MULTIPOINT VC_API OVERRIDE: endConference
232434.081828 userIDToCallIDMap count = 1
232434.081861 key: [email protected] - call id: 1
232434.081955 ### NEW STATE: to: VC_DISCONNECTING, from: VC_BUSY
232434.082173 SIPHangup start...
232434.082195 Stop heartbeat to w.x.y.z:49389
232434.082290 TANonInviteClientProc Thread start...
232434.082328 ( )( )( )( )( ) TP IS BINARY? (0)
232434.082343 Send to w.x.y.z:49389 [BYE sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK18de0342452c2e0e
Max-Forwards: 70
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 4 BYE
User-Agent: Viceroy 1.3
Content-Length: 0
232434.083238 ### NEW STATE: to: VC_IDLE, from: VC_DISCONNECTING
232434.083267 ++++++++ confStatusMapRemoveAll
232434.083278 ( ) -- mapUserIDToSecurityInfo cleared --
232434.083333 Conference_RecvThread end
232434.099205 =================== ActiveCount -= 0
232434.100129 ICECloseHandle ... done.
232434.112543 [[SIP/2.0 200 OK
Via: SIP/2.0/UDP a.b.c.d:42454;branch=z9hG4bK18de0342452c2e0e
To: "[email protected]" <sip:[email protected]:16402>;tag=617881761
From: "[email protected]" <sip:[email protected]:16402>;tag=90480416
Call-ID: e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173
CSeq: 4 BYE
User-Agent: Viceroy 1.3
Content-Length: 0
]] from w.x.y.z:49389
232434.112588 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232434.112687 Dialog Match(STATUS): [e7561234-6d6b-11dd-92ab-c7cb4b454012@10-0-0-173]=[e7561234-6d6b-11dd-92ab-c7cb 4b454012@10-0-0-173], [90480416]=[90480416], [617881761]=[617881761]
232434.112747 SIPHangup stop(0)...
232434.118393 Found 1 cameras:
232434.118452 Built-in iSight - 18446744073663414272
232434.118491 selectedCamera GUID returned Built-in iSight
232434.121955 Microphone devices:
232434.122053 Internal microphone
232434.122119 Line In
232434.122172 Selected mic: Built-in Microphone / imic
232434.130991 selectedCamera GUID returned Built-in iSight
232434.131225 Selected microphone is Internal microphone.
232439.112934 TANonInviteClientProc Thread end(0)...
232452.333136 TANonInviteServerProc Thread end(0)...

How to remotely "wake up" a Mac in order to screen share in iChat?

Apologies if this is not the right forum for this question.
I help my mother-in-law (81yrs) to maintain her computer (upgrades and all non-daily activities that she does not want to bother with) by remote Screen Sharing through iChat. This now works quite well.
However in order to screen share, her computer must be constantly ON, i.e. not be in sleep mode. Is there a procedure which would allow her computer to be turned into sleep mode after a certain amount of inactivity, but then be "woken up" remotely in order to do screen sharing?
Thanks in advance for any advice/suggestions/pointers.
Cheers from the Austrian mountains.
Veit

Thanks, Andy.
In another forum http://discussions.apple.com/thread.jspa?threadID=1340923&tstart=0 we found perhaps not the ideal solution, but a workable one.
Cheers,
Veit

Im trying to screen share on ichat but my buddies chat says I'm not available when my chat says i am... so whats the problem?

im trying to screen share with a buddie on ichat but on my buddies ichat it says im invisible when i really am available and my ichat says im available>\. So im wondering how to fix this problem!

Hi,
If this is iChat 6 then go to the General Section of the iChat Preferences
Untick the Link Buddy lists option.
Then check the Status for each Buddy List
10:22 PM Thursday; August 25, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

IChat screen share... what else?

I persuaded my Grandparents to buy Leopard specifically for screen share, but no luck so far. In fact, being home, I'm sitting in their house right now sharing their internet with airport and I STILL can't get even audio to work. I can connect with Leopard's screen share facility and with Chicken of the VNC easily, but not with iChat.
I wondered about .Mac though and the back to my mac feature. If anyone out there has it, does iChat work any better for you? With the persistent share, I figure maybe it would be easier to resolve the connection.

Okay, so I have it working... not sure what I changed, though. CotVNC does work after setting default profile to "let server decide" for color scheme. I was hoping to take it black and white to improve performance, but no can do I guess. It's a little picky if you want to kill the audio portion by turning off the mic. I can't get it back unless I quit out of iChat completely.
Nevertheless, it's working and one satisfied customer. It's speed is better than any VNC through home networks I've ever used, and the ease of connection (once you get it, of course) is equally impressive. Though I would appreciate a key combination to switch between my screen and the shared screen without having to have them stop what they're doing so I can navigate down to my window.

IChat Screen Share Audio

Hello,
Does any know how to turn off the audio portion of a screen share in iChat?
Thanks!
ebrind

I've received a similar error message. Try reducing the Bandwidth limit in iChat preferences. If it is set to "none" then I suspect you are experiencing the same phenomena as I have experienced. This occurs when multiple users are running under a mixture of broadband technologies and efficiencies. e.g. DSL vs. Cable. Satellite broadband can be worse.
We theorize that your/our Cable broadband bandwidth is so fast that the sync'ing or handshaking between the machines is outrunning one or all of your participants. This situation would occur when you or one of your participants is running broadband under DSL and the other(s) are running under Cable broadband. So if you're running at a 15Mbps download stream and a 2Mbps upload stream and one of your friends is running on DSL usually 768/368Kbps then there is a broadband mis-match. You'll "time-out" on the sync'ing and handshaking hence the error "you did not respond"!
Try resetting your Bandwidth Limit in iChat Preferences/Video to 1Mbps, and restart iChat. If that doesn't work reset to 500Kbps/restart etc. until it works.
Plz post if this resolves the problem.
Message was edited by: Russa

Ichat screen share: a way to limit to screen watching, not control?

hi - using Snow Leopard 10.6.8 on Workstations; is there a way to limit the screen share option so invited chat members can only observe the live screen of another member, as opposed to also having control of the other member's desktop?

Thanks for the points.
(Sorry it was not the answer you wanted to hear).
8:09 PM Wednesday; August 17, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Can't Video Chat or Screen Share with iMessages to iChat?

So I just recently got a new MacBook Pro with Mountain Lion to replace my white MacBook running Snow Leopard. I noticed iChat has been replaced by iMessages. All of my other Mac friends still use iChat. I didn't think this would be a huge difference, but I can no longer video chat or screen share with them.
I send them an invite, and they get an IM saying "[account] has sent you a video chat request". I'm registered under my AIM account, and so are they, so that's not the problem. When they send me invites, nothing happens. I get no notification, and it just shows "Waiting for response from [account]."
So I thought "okay, I'll just re-download iChat from a third-party site".
The download link just takes me directly to Apple's page about Mountain Lion. So that's out.
There's no option in my security on iMessages to override this issue and allow unknown developers. I have "Allow AOL's servers to relay video chats" option selected under Privacy, and that does nothing, either.
What's the deal? Can I no longer video chat (or screen share) with "third party" chat clients via iMessages anymore?

Hi,
I have tested my Messages (Ver 7.0.1 in OS X 10.8.2) to various versions of iChat (3, 4 and 5)
iChat 3 can send invites and open Video (Or Audio Only) chats to Messages.
The iChat 4 and 5 can Video Chat To and From Messages. (I was using AIM as I have more accounts I can play with)
I have even done 3 way Video chats in both Bonjour and AIM login using Messages and iChat 4 and 5.
I have just double checked between Messages and iChat 4 Offering the Messages Screen to the G4 (iChat 4) and I was successful.
Screen Sharing requires a Random port for the VNC connection that does the "picture" bit.
However if you had it working in iChat then this should still be working in the Messages set up. (Basically your router is doing UPnP or is an Apple Base Station doing Port Mapping Protocol)
Also iChat will not work in Mountain Lion (even if you grab the iChat 6 version)
Each version is very specific to the OS version it is with.
For instance during OS X 10.4 it got to OS X 10.4.11 but during those same increases iChat got to version 3.1.9
There was no update to Messages until OS X 10.8.2 making Messages version 7.0.1
Those small changes tend to mean that version 7.0 will not work with OS X 10.8.2 ( or the other way round)
It is all to do with the support apps and frameworks that help the app to work.
10:08 PM Saturday; November 10, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images."  No, Seriously

IChat video & screen share failure

using iChat 5.0.3 on a new iMac. I can initiate a request to share screen or video chat but fails to start. I am on 10.6.4. Under connection doctor, Router type light is YELLOW and states it is Symmetric and that the network's setup includes one or more devices that are not fully compatible with audio and video chatting.
What gives? It used to work fine on a previous iMac here. Sounds like a network issue but don't know where to start.

Hi,
This is a link to a Site Called Port Forwarding and the info for TX 170 (they did not list the TZ 100)
Do this pages look similar to yours ?
The third Sonicwall pic shows the Firewall > Services page open (where Port Forwarding is done.)
We are not looking at this stage to Do Port Forwarding.
In Firewall > Advanced does it have UPnP ?
Are there any Port Forwarding settings made ?
Are they for iChat ?
On your TZ 100 pages does it list an IP the ports are pointing to ? (Port Forwarding in many devices lists an IP (Computer) that has access to those ports - excluding others - possibly you new computer if it has s different IP)
I see here that it has Stateful Packet Inspection (SPI) which can be a feature that gets in the way of iChat.
I cannot read anything there that says it does UPnP.
You may also need to look and what it is doing for VoIP.
VoIP is Voice over Internet (IP Phones and devices) It uses the SIP (Session Intiation Protocol) to connect either a device (phone or adapter) or in some cases software that acts like a phone over the internet.
However iChat also uses SIP to connect.
VoIP used to be pushed over port 5060-5063 and some devices still make sure all SIP data uses one of these ports (5060 is the most common).
iChat does not use port 5060 for SIP since iChat 4 came out and any redirection by the TZ 100 maybe the issue.
If you cannot find UPnP on any page on the device you will have to set Port Forwarding.
You will need these ports
||iChat Ports||TCP||UDP||
|AIM|5190|5190|
|A/V|none|5678, 16393-16402|
|Bonjour|5298|5297, 5298, 5353|
|Jabber|5220,5222, 5223|none|
Note this is the iChat 4 and 5 Range
Add port 5060 UDP for iChat 2 and 3 and extend the group of 10 to 16384-16403 (20 ports)
iChat 4 and 5 also uses an undeclared Random port to do the Screen Sharing part and works if you can and do use UPnP (Or Port Mapping Protocol) to open ports in your routing device.
As you cannot set the random port you will not be able to Screen Share.
10:18 PM Thursday; September 16, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

IChat AV Auto Accept text messages causes app crash

I'm not sure if anyone is experiencing this but I just started using iChat after years of a hiatus. I noticed that there is an applescript for auto-accepting new text IM messages, a welcomed option.
However, ever since I turned it on, iChat crashes almost every time a new chat is started. Has anyway experienced this and, if so, are there any resolutions other than disabling it?
One thing to note is that I am running the Chax iChat add-on to integrate my AIM and GChat lists into one.
I'm running on a thunderbolt 15" MBP and OS 10.6.7.
TIA!
Brian

Hi,
So the Specs did not get changed :-)
Which version of Chax ?
IF you used the .dmg for the Leopard version you may have a problem.
In Console (Applications/Utilities) is it managing to save a Crash log for iChat ?
You have to open the reveal triangles
10:46 PM Thursday; June 9, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.7)
 Mac OS X (10.6.7),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

IChat Auto-Accept Screen Share

Similar Messages

Maybe you are looking for