On Mon, Feb 8, 2010 at 11:46 AM, Michael Scheidell <[email protected]>wrote:

>  diagnostics?
> not bloody useful for anything at all, unless you drop to cli, do tcpdump
> or wireshark traces, or use siptrace (and X windows to follow it)
>
> so, where in the GUI would I see anything at all? including that the trunk
> wasn't even registered anymore?
> heck, where in the GUI would I see that the trunk registered?
>
> needed to watch wireshark and registrations failing, then I got a new
> account password.
>
> then.. when I tried to use skype sip for ip (instead of username/password),
> you can't even see packets.
>
> so, where would I look in the GUI to see that the trunk is registered or
> not?
>
>
> --
> Michael Scheidell, CTO
> Phone: 561-999-5000, x 1259
> > *| *SECNAP Network Security Corporation
>
>    - Certified SNORT Integrator
>    - 2008-9 Hot Company Award Winner, World Executive Alliance
>    - Five-Star Partner Program 2009, VARBusiness
>    - Best Anti-Spam Product 2008, Network Products Guide
>    - King of Spam Filters, SC Magazine 2008
>
>
> ------------------------------
>
> This email has been scanned and certified safe by SpammerTrap®.
> For Information please see http://www.secnap.com/products/spammertrap/
> ------------------------------
>
>
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
>

I think you are doing some things "wrong".

1. You would create the sip trace file and copy it to your PC and run
sipviewer from a workstation. X does not have to be installed on the server.
That works "and always works". It indicates to me you are probably doing
this in the hardest possible way.
2. You assume Skype is far enough along that they would provide anyone with
the information for the skype sip for business function to be able to
acknowledge this or write it into their platform.
3. You assume Skype is reliable at this stage. If they won't provide support
for it, and are charging you, it points to the fact that it probably cant be
relied on at this point, at least by you.
4. Skype's BETA has known bugs, which they haven't, and in some cases won't,
fix.

Let me share some relevant points about "skype" in general:


   - They have barely any infrastructure to support a real voice network.
   Their switching platform is thousands of peer-to-peer applications on the
   Internet on home PC's, sort of a virus-like in the approach it takes to
   circumventing a lot of security software. Why any business would use a
   non-facilities based provider for voice services is beyond me.
   - They thumb their noses at US law (FCC mandates) to comply with CALEA,
   which all real providers have to abide by "here".

If noone is giving you any real responses to the "Skype" question, it's
likely because noone is wasting that much time on it because of their
platform issues.
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to