Screen Share-No audio
I just set up my mac mini snow leopard server. I have an external hard drive connected to mac mini with movies on. When I do a screen share on the mac mini with my macbook air I don't receive audio. Suggestions?
If the drive itself is mounted on the mini, and is included in the items shared from your mini, you could just try to watch it directly by opening via a media player installed on your Air. Because you'd be pulling it from the drive, then to the mini, then across the network this might be slow and stuttery. Other options involving media center applications like XBMC, or my favorite Plex can perform media serving functions which can also transcode the content for better quality streaming. VLC also has a server version which you could run on the mini and watch via VLC Player on the Air. These solutions are designed around exactly what you want to do.
Similar Messages
-
I need to be able to hear the audio through THIS computers speakers, from a computer I'm screen sharing in another room of the house. I seem to only be able to get audio from the computer I'm sharing, not this one I'm using to control that shared computer.
Is there any way to get the audio to come out of the controller computer, not just the host computer?difficult, after all it's screen sharing not audio sharing.
you could try ichat. it allows a screen sharing session with audio enabled. but if you play the audio through speakers, it's likely to create a feedback loop because the sound that is played through the speakers is picked up by the mic, which plays it on the speakers and so on.
I think with OS X system tools this cannot be achieved, sorry -
Hello,
Does any know how to turn off the audio portion of a screen share in iChat?
Thanks!
ebrindI'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 -
Can video/audio chat but not screen share
Have been trying to screen share for the first time. Audio and video chatting work fine, but when trying to screen share with the same user it fails due to "unknown connection error". We are both using .mac accounts.
Firewalls are turned off. The only thing I have noticed in looking into different reasons why this might be happening is that my connection doctor says I have a "symmetric router". It is a linksys WRT160Nv2.
Any ideas?Hi,
Welcome to the Discussions
How have you got the ports ichat needs open in the Linksys ?
The Screen Sharing uses a random port that is not handled if you are using Port Forwarding, DMZ or Port Triggering.
Cancel/Disable any of the Above and go to the Administration page and enable UPnP
(Apply/Save Settings)
10:04 PM Wednesday; June 2, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat" -
Audio with Screen Share?
Is there any way to get the audio from a computer that you are connected to with screen sharing?
I often work from home and use Screen Share to connect to work computer. It would be extremely helpful if I could hear the audio from that computer. I don't expect crystal clear audio, just enough to hear in and out points on quick edits.
Thanks,
Heatheri've never heard of audio coming across the screen sharing window... would like to know more, if it is an option... is it an option in preferences or something?
The reference to iChat was audio converstation with the person on the other end while you are trying to diagnose their system.
It is NOT the remote Mac generated audio.
regarding iChat, last time i heard, iChat requires a dotMac account for most of its features...
iChat works with AOL Instant Messaging (AIM) and you can get a free account. I have been using this with my Mom to do text, audio, and video chats with my Mom since Mac OS X 10.3 came out.
And more recently iChat has added support for XMPP (aka Jabber) instant messaging networks. I use XMPP with my companies IM service, as well as Google's GTalk IM service.
i only occasionally use iChat with google, but no audio goes across, nor file xfers... i don't know how iChat would work either since i think iChat would require someone to be at the destination computer to accept the connection... do you have more info about how this works and what "network servers" it requires to work?
A donation-ware plug-in extension for iChat called Chax adds a iChat preference option to auto-accept an invitation to share the screen for a list of specified users.
But again, this is ONLY useful for getting audio from the person sitting on the other end.
But the auto-answer for screen sharing can help solve the, how do I get through the home NAT router and how to I find the remote comptuer. iChat is providing that service. -
Video / Audio / Screen Share have all stopped working...
I've got two business partners in remote locations. All three of us are on MacBook Pros. Mine's several years old, but theirs are both new. We're all using MacOSX 10.5.6 and iChat 4.0.7. All three of us have been able to do video, audio and ScreenShare with no problem up until last week. To the best of my knowledge, none of the three of us has had a hardware change or a software change. We can chat fine.
Every time any of us tries to initiate video, we get "Waiting for Response"... then "Starting Video" when he accepts... then "There was a communication error during your chat"... "Did not receive a response from X" when in fact he is clicking accept.
Enable Screen Sharing / Video / Audio is all selected in the iChat video menu. Based on previous threads I'd read, we've also tried the System Preferences / Sharing settings, unchecking "Remote Management" and checking "Screen Sharing". Nothing's helped so far.
One of us is on a Linksys router (me), one on an Airport and one on a Netgear router. Again... all worked fine until last week. Any help you can offer would be greatly appreciated.
Any suggestions would be greatly appreciated.Hi Skippy,
Welcome to the Discussions
It is difficult to say what is going on here and three people with different routing devices all seem to have the same problem at the same time.
My firts thought would be that if the routers are doing DHCP to the LAN (computers) and that POrt Forwarding was also used the IP the computer has may have changed and the Port FOrwarding will not be pinting to the IP the computer now has.
However this is unlikely with three devices at the same time.
The Netgear is also probably doing UPnP by default and therefore not doing Port Forwarding.
Te Linksys can do UPnP but needs it Enabled.
The Airport does something called Port Mapping Protocol (Apple's version of something similar to UPnP) and needs it turned on.
Again it seems strange that buddy to buddy individually you are all having issues.
Are you all using the same ISP ?
Has there been a Speed bump in service ?
From Table 1 can any of reach the Apple test accounts ? (Uue the ones that end in @mac.com)
8:40 PM Saturday; April 11, 2009 -
Video and Audio work but not screen share
I am able to connect and video chat with a mb running 10.5.4.
When I request screen share, they authorize, seems to start to connect then I get the message "screen sharing could not be established."
Is this a port issue?
Thanks in advance!Oh My !! You are doing things the difficult way.
Hopefully you have got both ends set in System Preferences > Quicktime > Streaming to 1.5Mbps
(if you have to change iChat will need restarting).
In the iChat Menu >Preferences > Video Section > Bandwidth drop down both ends need to be on 500kbps to get around what Comcast and Road Runner do to manage their Data Stream. This can be set in a chat. The two ISP s do things to try and stop people using File Sharing apps like BitTorrent but it impinges on iChat.
The reason why I say it is a port issue.
I run an App called Little Snitch.
It tells me the ports and the IPs applications are connecting to.
In a successful Video chats I see port 16402 on people's Public IP and if they have a Router a LAN IP as well.
When in a Screen Share situation I also get another port.
Screen Sharing in iChat iss related to the way it is/was done in Apple Remote Desktop (ARD).
in fact in the iChatAgent .plist you can see the Setting
(It is in fact Off in this Pic)
Apple Remote Desktop uses port 5900 and 5988.
However, Little Snitch reports to me a fairly random port when I use it and shows a number in the 50000 range.
I use UPnP in my combined Modem/router which seems to cope with this random port.
UPnP (Universal Plug and Play) allows any port the App wants to open to be open - control is with the App.
This Doc by Apple tells you the ports to open if Port Forwarding for iChat 3
It includes the Bonjour ones, the Jabber ones the AIM ones and the A/V ones.
http://support.apple.com/kb/HT1507?viewlocale=en_US
This second Doc by Apple is about the port changes to iChat 4
http://support.apple.com/kb/HT2282?viewlocale=en_US
This one only tells you about the A/V ports and not the other you need.
AS it is short on info that is known about it stands to reason the info on Screen Sharing ports is also missing.
This link is about the Linksys WRT54GS
http://portforward.com/english/routers/port_forwarding/Linksys/WRT54GS/iChat.htm
Near the top of the page is the Info to use in a web browser to access the set up pages.
Follow the Instructions to to access the device and set the Unblocking of Anonymous Pings in the Security page.
Stop following the Instructions and go to the Administration page.
In here you will find UPnP.
This should be Enabled (Save Settings if you need to)
You will see in the rest of the Instructions that Port Forwarding is in Applications and Gaming as a sub tab. If anything is set here it will need to be Disabled.
As will anything in Port Triggering and DMZ tabs.
The Linksys WCG200
I can not see the one with cc at the end on the Port Forward.com list so I have picked version 2
http://portforward.com/english/routers/port_forwarding/Linksys/WCG200v2/iChat.ht m
You can see the pics are similar.
Although it does not say, also disable the Block to Responses to Internet Pings on the Security page (as well as having the Firewall Off).
Then do the same as above. Enable UPnP and Save Settings - Disable anything in Applications and Gaming and again save settings.
As I said before UPnP will allow the apps to open the ports they need and will therefore cope with the fact we don't know the precise port iChat is supposed to use.
Out of the Box list.
Apple have a list that was started at iChat 2
http://support.apple.com/kb/HT1787?viewlocale=en_US
Although the Doc was updated in June this was only for the new numbering system.
You will notice under the table that some still need tweaks.
Realistically most devices will need some tweaks and turning on UPnP can be the smallest.
Most Netgears have UPnP on by default.
However they have the Internet Ping Blocking and they have a DOS or SPI firewall that can impinge on iChat 4 as all the data is on one port and Faster internet speeds mean more data can be sent bumping into the threshold that these work (And get in the way).
MIMO devices that tend to come with two or more antenna are a problem for iChat as the Wireless signal is effectively duplicated and iChat see this as two network connections and can not use them - if you are thinking of being wireless.
9:04 PM Wednesday; August 20, 2008 -
How can I use screen share of my mac mini? Problems validating
I recently purchased a mac mini to act as my home media server for audio as my airport express was not playing nicely with my Peachtree DAC. Anyway, I have set up sharing on the mac mini and can't figure out how to connect from my wife's Macbook, or her iPad. (I use a PC, so would welcome advice if available on how to connect across platforms as well.) My goal is to set up the mac mini without a monitor or keyboard connected to it and have it sit with our main stereo.
I am able to connect to the mac mini via my wife's macbook IF I ask for permission and I grant it from the mac mini. However, I am unable to connect no matter what I try if I try to log in as a registered user. I have tried to add her as a user to the mac mini, I have tried to log in as a guest, and I have tried to log in with a password but no matter what I try, I get an authentication error when I try to log in as an authorized user. For more clarity, here is what I have tried:
1. Added authorized users on the mac mini. I created a user name for "jeff", "maureen", and "lastname_maureen" on the mac mini and provided a password for each user. "jeff" and "maureen" are just created on the mac mini, and "lastname_maureen" is the user name of my wife's computer. I confirmed the passwords, and still am unable to connect. I have allowed any user on the network to access screen share, and no matter what I do I get an authentication error. Again, if I attempt to log in from my wife's computer by asking permission, it works fine but I can't figure out how to set up an account to login. Please help. Thanks!Have you tried connecting one to the HDMI output, and another to the Thunderbolt port (with the appropriate Mini DisplayPort-to-other connection adapter as needed)?
-
CAN'T SCREEN SHARE! TRIED EVERYTHING! PLEASE HELP!
My girlfriend just got a new Macbook and I've been helping her set it up across campus though our network at my university. It worked fine and then one day it didn't. Every time she asks or I ask to share her screen it gives this error to both of us:
"Failed to start Screen Sharing because: Screen sharing could not be established."
I've been reading discussions on how to fix this for 2 weeks now and nothing has seemed to work. What is weird though is that I can screen share PERFECTLY with my Uncle who lives in Wisconsin (I am in Arkansas) from campus. However, I can't seem to connect to my girlfriend's computer who is simply just a few buildings away.
The following is what we've tried:
1. Switch from wired to wireless network
2. *Set "System Prefs>Quicktime>Streaming" to "1.5 Mbps T1/Intranet/LAN"
3. *Set "iChat Prefs>Audio/Video>Bandwidth Limit to both "500" and "None"
4. *Both computers have a firewall set to "Allow all incoming connections"
5. *When #4 didn't work we set firewall to "Set access for specific services and applications > iChat.app set to "Allow incoming connections"
6. Rebooted both Macs
7. Deleted all com.apple.iChat.X.plist files and started over fresh
8. *Enabled "Screen Sharing" in System Prefs>Sharing
*Restarted iChat afterwards
I think that's all. It is just really frustrating because I can screen share with someone clear across the nation but not someone who is on my same network. The only difference is that she is using a Gmail account through AOL and I am using a @me.com address. I thought maybe Gmail wasn't working so I had her switch to an AOL account and still same error.
We cannot port forward for obvious reasons at school but it worked before and nothing on the firewall has changed. I work at the IT department at our university and spoke with the person who runs the Firewall and supposedly there are no blocked ports on the part of the network we use. I know with iChat 4 in Leopard it doesn't use a specific port, it bounces around until it finds one according to article regarding port forwarding and NAT routers and iChat.
The weird part is that when we are both off campus (different houses) and try it, Screen Sharing tries to start, she gets the big words across her screen ("Screen Sharing Started" I think...) and we can hear about 5 seconds of audio and then it errors out again. I really want to get this working can someone please tell me how? This is really frustrating.
Thanks,
-jgHi,
First off from reading this it should be an AIM valid name (@mac.com, AIM or @me.com) to AIM valid name or
a Jabber valid name (which includes Googletalk valid Gmail IDs) to another Jabber valid name
(that is both should be using the same type of Buddy list)
As you say the Apple Doc on this is not clear on the Screen Sharing part - listing only the changes to the AV ports compared to the Previous Doc (Now article HT1507). It does not mention the Screen Sharing at all.
Reading around suggests the Screen Sharing is based on Apple Remote Desktop and reading the com.apple.ichatAgent.plist with QuickLook shows a reference to a ARD link/process. (the same can be seen if you install Developers Tools from the Install disk which will give you Property List Editor which will open the .plist files).
The Article TS16929 (Previously Doc 106439 shows that Apple Remote Desktop uses port 5900 and 5988.
Having said that though I run Little Snitch, an application that monitors and reports which IPs and Ports and application is trying to use. This shows me a completely random port in the 15xxx range along side the AV port 16402 for the Audio component. It maybe that Apple Remote Desktop also moves to a random port after it has established a connection.
Most people fail on the Audio part and get the standard Log Pop up screen to send or not to Apple - BUT you clearly have the other message...
"Failed to start Screen Sharing because: Screen sharing could not be established."
.... which is unrelated to the Audio part.
This would clearly put things in to the realms of a firewall or setting issue with possibly modem/router or LAN features getting in the way. (Leaving aside ISP related things for the moment).
You say iChat is in the Allowed Specifics List in the Leopard Firewall.
You say that nothing has changed on the Campus Firewall and can connect Off-site form On-site so it would seem not to be there.
On this last issue, check if they have introduced a Streaming cap on Intra-Site links. They may be trying to prevent other things such as Peer-to-Peer File Sharing or thing like everyone sharing their iTunes Libraries and other similar activities. The ability to Share Optical Drives re MacBook Airs maybe a factor.
I would tend to look towards your girlfriend's Mac.
Since iChat 2 it seems that some failed chats seem to hold on to ports or have some hold over the Network going on.
It seems most common when in System Preferences > Network the drop down at the top listing "Location" is left at the Automatic Default.
There are essentially two fixes for this.
1) Set up another Location and copy the settings across and switch between the two to force the Network to re-establish itself.
2)A longer way of clearing what is going on.
a) Shut any Airport card down if using WiFi
b) Shut down the computer.
c) Disconnect any Ethernet cable from either Computer or routing device (whichever is easier to reach but leave the routing device still connected to the Internet - just isolate the computer from the Internet)
d) Restart the computer (this is with no Internet Connection)
e) Restart iChat.
f) Restart Airport card or plug in Ethernet cable.
g) Using the Buddy List, select Available and make iChat Login (can also be done from the iChat Menu (> Accounts submenu in iChat 4)
On your last paragraph I would ask if you can Video chat at this set of locations ?
This is because in this scenario a feature of one of the modems may be an issue.
Some modems and routers have DOS (Denial of Service) or SPI (Stateful Packet Inspection) protection. These tend to be threshold based and have no setting control in the devices set up pages (other than On or Off).
iChat can stream so much data, particularly in Video chats over what are now quite high Internet speeds that a DOS feature will consider it an Internet attack and cut the port involved. SPI tends to be judging whether the data stream is valid and does not seem to keep up and the result is the same.
In Video chats the end that has the Problem tends to get a Error -7 In the Log.
The Other end gets the "No Data for 10 Secs" message.
Summary.
Essentially though as you have tried a deletion of all the .plists for iChat and you imply both ends it is more likely something about the Network or how the Mac thinks Network resources are already allocated.
There is not an easy .plist deletion for this hence the two methods listed above.
NOTEs: 1) #8 in your list is not related to iChat.
This is what you can now use of Apple Remote Desktop itself. It has it's own Screen Sharing app (without Audio like iChat) that is invoked from the Finder's Go Menu > Go to Serve and entering a VCN:// IP address. (As a System Application, as it were, it is in /System/Core Services/Screen Sharing.app)
It does need both Macs to have the Setting Enabled as you have done it #8 though
2) Some ISPs it is suggested block Screen Sharing. (Verizon was the name I heard mentioned). How they tell what the data steam is specifically I do not know as it would seem that the Audio part of an iChat Screen share would make it look like an A/V chat and that Apple Remote Desktop must be a valid way of working for some people. However iChat is Peer-to-Peer in AV chats and Screen Sharing and some ISPs are known to actively work against these file sharing apps that bear the same generic term.
In your case I do not think this applies as you can Connect Off site via whatever ISP your Campus uses.
I hope this helps.
9:58 PM Wednesday; October 1, 2008 -
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)... -
Does video chat on the new Messager on Mac allow screen share or multiple people?
does video chat on the new Messager on Mac allow screen share or multiple people?
i noticed they said that facetime will basically be taking over video calls on the mac and that Messager will take over ichat, but i'm worried they're going to drop all the nice features they had on ichat, like being able to share screens while video chatting with someone. or being able to chat with 2 people at once on a video call.
has anyone downloaded the beta of this yet and tried it out? i'm very curiousHi,
You can start a Video chat with one Buddy and then chose Screen Share and providing you and the Buddy are using UPnP to open ports it will instantly convert to a Screen Share.
A Screen Share is only 1-1 and is technically an Audio Chat +
The Plus bit is an VNC connection alongside the Audio Chat.
This VNC connection uses a random port - hence the need to use UPnP to open the ports in the router (Or Port Mapping Protocol) in Apple Base Station.
There used to be Add-ons that allowed the Desktop as Video Feed which would have been a sort of Screen Share but none of these have been updated for Lion.
An Example is iUSBCam (ShowMacster was another - My link no longer works)
CamCamX maybe a possibility if it works in Lion (It does say it neess iUSBCam for iChat)
10:56 PM Thursday; February 16, 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 -
Screen Share - Change what to display & video quality
Hi LCSS Team,
I have been playing around with screen share and have it working in collaborative (both ends can share/control their screens).
Upon initial selection of deskop/app/window, is there a way to allow users to change what to display without having to
start/stop?
Use case:
- User A is viewing user B screen. User B would like to change view from desktop to a specific window.
Also, the screen share video feed is very pixelated. I have tried it multiple settings including what you guys sent
me. I am trying to get it to Skype like quality. Is that even possible?
Thanks,
MichaelHi octoguy,
iChat makes hardware and connection speed checks as it starts up.
This gives you the framerate and bit rate duirng a call.
Lets say that your processor gives your iChat 15 fps
This will be the rate that you will then see to a another Mac.
The same computer is likely to get 10 frames per sec to a PC.
This is some part due to the PC putting a fair amout of effort into producing a clear detailed pic.
On some PCs this setting for the video pic is so high that the audio will drop out completely.
The cure is to bring the PC preview to the front (tabs)
Then click on the small icon that appears to the right and adjusting the slider that appears to the left.
This will incease the frame rate and bit rate from the PC. It makes the video look smoother although the actual quality has gone down (you may not be able to judge this quality difference by eye)
As general rule you will get about 2/3rds of the normal Mac to Mac framerate shown in the Connection Doctor. It also seems to take about 50% more Connection speed to get the same quality video.
So Mac to Mac min is 100Kbps where as Mac to PC will need about 150kbps.
The quality drop from 15 frames a sec to 10 frames a sec does make the video generally more blocky but does also depend a fair bit on the processor power of the PC and the camera used.
I know that sounds a little vague but there are really many variables that can be a factor.
11:23 PM Monday; April 24, 2006 -
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. -
Please Help! i am trying to screen share between a macbook pro and macbook. i can video chat, but when i try to screen share, sharing initializes for a few seconds, but then stops and an error comes up: "no data has been received for 10 seconds" and it asks me if i want to report to apple. in those few seconds i can open files and interact with the other screen, but then the error occurs. both computers have 10.5.1.
Message was edited by: worshipgzsDane and I have briefly chatted about this.
The same computer in the work situation could not Video chat (different Error number)
Error 20 is normally put up if the connection is cut.
This could obviously be a faulty WiFi card,
A specific response from the type or the amount of data in a router's SPI or DOS protection.
iChat uses two random ports for the Screen Sharing and then the Audio part is on port 16402. It is this bit the Error Log points to but message about not Connecting is often on screen before the log comes up so I would not hold out that it is the Audio part.
In Dane's case it was clear by using Little Snitch during the attempts that he was behind at least two routing devices and possibly sitting in two subnets.
He was not able to tell me more about the set up or what he had at home.
6:07 PM Friday; January 4, 2008 -
New DSL connection prevents screen share, videochat
Previously, I was able to videochat and screen share with a remote computer using ichat. With that particular remote computer, I was never able to use vnc or finder-originated screen sharing, so I've always relied on ichat.
I switched from cable to Verizon's DSL internet service, and now I find that I can no longer screen share using ichat or use videochat. Sometimes my file sharing is also affected. I can also no longer access this screen from another computer from the finder, or access this computer as a file share from another computer.
I have enabled file sharing and screen sharing in the sharing panel. The remote computer also has screen sharing enabled. I have mobile me service, which syncs ok, and I can obtain a shared screen from my office computer, although this seems to be available only now and then.
Running ichat 4.0.8, OS 10.5.7 on both computers that I'm having trouble screensharing and videochatting between.
Any suggestions?
Thanks
ToddHi,
I have seen one post that remarked that the end user thought Verizon were now blocking VNC connections and that their reasoning was to stop Internet attacks on Home computers.
Seeing this is a common method for large companies to update remote computers particularly with Windows and is part of Apple Remote Desktop, And, that on all computers it has to be set to be allowed, this did seem a bit lame.
If you know the IP addressing needed to get from home to your work computer then using vnc:// instead of afp:// in Connect to Servers will invoke the Screen Sharing App that is hidden away in Leopard in Hard Drive/System/Library/Core Services (I have only done this over my Local LAN and don't know how to set it up or address it over the internet)
Your extras clues only seem to partially support the idea that VNC connections are blocked.
If Video chat were not working as well I would look to whether the Modem is allowing Response to Internet (Anonymous) Pings as I know iChat sends a Ping in Video and Audio Chats (and the screen Sharing includes a Audio feed.)
I would have looked on this site for more clues http://portforward.com/routers.htm as some of the Instruction pages include pictures that can be helpful in some cases.
I don't see your model listed which may mean it is really new and has not made it to the list yet.
Defcom either compared them a chose the most likely access defaults or found the info elsewhere.
This one which may be the closest model number has no real pictures in this case
http://portforward.com/english/routers/port_forwarding/Westell/D90-740010-06/iCh at.htm
This page is from a D-Link emulator
http://support.dlink.com/Emulators/di624revC/advfilters.html
It is Advanced then Filters (The Yellow items)
Do you have anything like this on your device ?
Does anything appear to be set ?
In this Tools and Misc page it has UPnP and other options that may need to be allowed. (WAN Ping Blocking is on this page for this device and it also has VPN stuff)
These pages/links are for clues only as most manufacturers of modems and routers layout the pages differently.
My thinking is that it is either something like a Firewall or filter or similar on the modem that need "Unblocking" in some manner to allow UPnP to "Fully" function or the ISP is doing something that they are not being too open about.
8:05 PM Monday; August 3, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
Maybe you are looking for
-
Problem with checkboxes in IR report mainly for update process please help
Hello, Can anyone please help me out with this issue. I have an interactive report with 3 checkbox item for a single column named status. Based on the value of the column status the check box should be checked. For example: DECODE(status,'DEV',1,0) a
-
I have 2 iphones, 1 personal and 1 business. I thought I was supposed to have 2 separate itunes accounts. I now have a work ipad and want to only have 1 itunes account that I can use for all 3 devices. How do I cancel 1 account or just combine the
-
I'm trying to make a presentation using 30 short video clips and several hundred photos. The video clips look great, however when I import the photos into iMovie, the resolution is terrible and extremely noticeably different than the same photos in i
-
CO-INTERFACE WITH-PS: Settlement of Project
Hi Friends, What steps involved in settlement of Project. In project system we find Top lvel WBS element under that we can find low level WBS elements and net works. To settle the project to cost center what are the object have to settle to what obje
-
Proper Backup Procedures with External Hard Drives
I use external firewire drives for all of my photos and I have a quick question about backup procedures. I currently use Intego's Personal Backup X5 software solution and I wanted to know whether it is better to backup your files or Sync your files w