tag:blogger.com,1999:blog-2158853543793456735.post819463411279078354..comments2023-10-02T04:50:01.667-07:00Comments on VoIPNorm's Collaboration Blog: Pre Call Diagnostic toolChris Normanhttp://www.blogger.com/profile/07200178774058910421noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-2158853543793456735.post-12599901769425190462010-03-19T11:24:37.717-07:002010-03-19T11:24:37.717-07:00This tool doesnot work and error's out with th...This tool doesnot work and error's out with the below message, The machine is joined to the domain but OCS R2 is installed in a different domain,is this related ? Communicator is configured for auto and has no issues connecting to OCS R2 environment from this pc.<br /><br />"There was an error starting the channel,<br /><br />There was an error signing into the SIP server using the sip URI you've configured.Please double check that the SIP URI is correct for the logged-on user,Also, this might indicate that the server might be temporarily down."<br /><br />AvinashAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-28461635946119466292010-02-11T13:58:10.505-08:002010-02-11T13:58:10.505-08:00This is a known issue and a fix is being incorpera...This is a known issue and a fix is being incorperated for a future release to the tool. I was unsuccessful at making it work on the current release of the tool.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-25752872071511862672010-02-11T10:47:02.146-08:002010-02-11T10:47:02.146-08:00Chris,
Have you had any luck making the tool work...Chris,<br /><br />Have you had any luck making the tool work on a machine that is not joined to a domain?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-62275294070838221582010-02-09T12:19:15.275-08:002010-02-09T12:19:15.275-08:00I think I get more from where you are coming from ...I think I get more from where you are coming from when you started to mention the current status indicators of poor network conditions. I agree the current client is challenged in this area and there is certainly room for improvement. Watch this space in the next release.<br /><br />Back to the very first comment about non domain joined computers. This is a known issue and a fix is being incorperated for a future release to the tool.<br /><br />Thanks for the great feedback from everyone it certainly keeps me motivated that I am bringing value in the information I am posting.<br /><br />Thanks<br />Chris (VoIPNorm:)Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-89852914834597173742010-02-09T09:58:31.030-08:002010-02-09T09:58:31.030-08:00Hi Chris,
First - I really get a ton of value fro...Hi Chris,<br /><br />First - I really get a ton of value from what you write (that's why I'm here) so a big thank you.<br /><br />I agree that if the tool is meant to help the 'average user' get some indication of what their experience may be - especially over an ISP, there is value.<br /><br />The danger is when this tool is given to users on an enterprise network that is designed to handle 'real time' traffic, then imply this tool can give an indication of what call quality may be. Context is everything and when it is missing usually means more work & problems created than problems solved. <br /><br />Thanks and please keep up the very informative and helpful talks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-51053006996130385282010-02-09T04:48:40.549-08:002010-02-09T04:48:40.549-08:00Chris:
(I wrote the 1st post)
this tool actually...Chris:<br /><br />(I wrote the 1st post)<br /><br />this tool actually sends about 10-15 UDP STUN packets/sec to the AV edge server. The response it gets back from the AV edge is used to guees/ calculate roundtrip time, jitter and packet loss. I think that amount of traffic is so scarce, it can only be used to see a really BASIC network quality.<br /><br />At the first time when I had no experience with this tool, my assumption was that this tool will actually visualize network conditions DURING a call. So I can visually see why that call was terrible: example I see the packet loss graph goes high and during that second I hear silence instead of the remote party speaking; or 2nd example: jitter graph goes high, and in parallel I start hearing the speaker talking in chipmunk style (2x times faster than normal) because packets was delayed in the buffer and now start to playback audio from the previous 4-5 seconds @ a faster speed.<br /><br />Communicator client by default has only 2 yellow exclamation marks for "poor" network conditions, but I cannot interrogate the client to tell me exact facts, why it is "poor". That tool was my expectation for the problem, but no luck.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-87381362540580060462010-02-08T10:38:33.337-08:002010-02-08T10:38:33.337-08:00The tool is really aimed at the average user to un...The tool is really aimed at the average user to understand network conditions to make a call similar to the indicator you get on a cell phone. Its not meant as a replacement for more complicated network sniffing or monitor tools. On the internet there is no QoS policy so any tool to help a user make a decision to use Communicator to make a call is in my opinion helpful.<br /><br />It sounds as though you are looking for a more comprehensive troubleshooting tool. There is a OCS VoIPtestset but it may not be as comprehensive as you would like as far as call quality goes. <br /><br />Good feedback that I can pass back to the BU. Thanks.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-55111432600041771472010-02-08T10:18:08.102-08:002010-02-08T10:18:08.102-08:00if the tool is no more intelligent than a ping, it...if the tool is no more intelligent than a ping, its close to useless. if the tool is intelligent and actually uses traffic patterns (or allows configuration) to mirror a network QoS policy, then there is some value. <br /><br />using bad data or a tool that does not understand the underlying network is more dangerous than helpful.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-66532975828155137612010-02-08T08:46:40.711-08:002010-02-08T08:46:40.711-08:00Hi,
#1 I am looking into this point. Even with a ...Hi,<br /><br />#1 I am looking into this point. Even with a machine that allowed Communicator to function without it being a domain joined machine it didn’t work. I will post back when I find something out.<br />#2 This isnt a packet monitoring tool like you suggest. Although this is much simpler it does provide some important troubleshooting information that can be collected over time and help troubleshooting flaky network connections. I still think you have an interesting idea but I am not sure the average user would be able to take advantage of this information. If the information can be presented in a understandable format so that a user could at least describe it to a help desk operator it may be helpful.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-22786260515576291682010-02-08T08:41:19.507-08:002010-02-08T08:41:19.507-08:00This comment has been removed by the author.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-73934271991154244742010-02-08T07:24:08.341-08:002010-02-08T07:24:08.341-08:00I agree with the comment above. I have not been a...I agree with the comment above. I have not been able to make this work on my workstation that is not a domain member. If anyone has any information on how to configure the XML config file, I'd love to hear it.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-70702747329435491162010-02-08T01:30:12.327-08:002010-02-08T01:30:12.327-08:00just 2 sidenotes:
#1 it is not trivial to make t...just 2 sidenotes: <br /><br />#1 it is not trivial to make that work if the computer is not joined to domain (at least I was not able to configure it, the xml config file has no documentation)<br /><br />#2 this tool is nothing more scientific than an ordinary "ping -t". I expected that this tool shows statistics of packets sent/received by the communicator.exe process, but no.Anonymousnoreply@blogger.com