Re: [Full-Disclosure] SIP client for *nix

harry_at_behrens.com
Date: 12/04/03

  • Next message: Olaf Kirch: "[Full-Disclosure] SuSE Security Announcement: Kernel brk() vulnerability (SuSE-SA:2003:049)"
    To: "Schmehl, Paul L" <pauls@utdallas.edu>
    Date: Thu, 04 Dec 2003 17:28:36 +0100 (CET)
    
    

    Dear Paul,

    if MS Exchange Server speaks standard SIP any *nix SIP Client should do at
    least the communication part.
    I think you will have a hard time finding a TLS-enabled SIP-IM for *nix.

    We (SNOM, www.snom.de) are currently developing such a client (actually a
    Linux-based SIP-phone) but it´s obviously not open source.

    In case of you wishing to use it in a pure academic environment we might be
    able to help you, if you´d be willing to act as a "reference cite" (I´d have
    to confirm that with our Marketing guys).

    Feel free to get in touch offline.

    Regards,

     Harry Behrens

    Zitiere "Schmehl, Paul L" <pauls@utdallas.edu>:

    > I've gotten a lot of answers to my post, and I appreciate every one of
    > them. Unfortunately, I apparently wasn't clear enough about what I'm
    > looking for.
    >
    > We have an Exchange cluster that is running the new Exchange Messenger
    > server which runs SIP and TLS. (The Windows Messenger client is
    > 5.0.0381.) This is brand new (for them) technology from MS and is
    > completely different from previous versions of Messenger.
    >
    > This allows our Windows users to chat securely, which means, for
    > example, that the folks in Registration can chat with the folks in
    > Records, exchanging private information such as SS#, birthdates, etc.,
    > securely without having to get up and walk over to the other office to
    > ask a question.
    >
    > Now we're looking for a SIP client that can utilize the existing
    > Exchange Messaging server to communicate securely with other clients,
    > regardless of platform, using SIP and TLS.
    >
    > We are not looking for VoIP at this time. We are not doing H.323 for
    > this particular application. We would prefer not to have to set up a
    > *nix proxy to handle communications between *nix clients and Windows
    > clients, but if that's the only option, we'll probably go that route.
    >
    > So, does anyone know of a *nix SIP *client* that can communicate
    > directly with Exchange Messenger Server? (I've already looked at a
    > bunch of sites, some of which folks on this list pointed me to, so I'm
    > aware that there are *nix SIP servers.)
    >
    > Paul Schmehl (pauls@utdallas.edu)
    > Adjunct Information Security Officer
    > The University of Texas at Dallas
    > AVIEN Founding Member
    > http://www.utdallas.edu/~pauls/
    >
    > _______________________________________________
    > Full-Disclosure - We believe in it.
    > Charter: http://lists.netsys.com/full-disclosure-charter.html
    >
    >

    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html


  • Next message: Olaf Kirch: "[Full-Disclosure] SuSE Security Announcement: Kernel brk() vulnerability (SuSE-SA:2003:049)"

    Relevant Pages

    • Re: exchange basics
      ... If you find users switching between client ... often pull the mail to a different store (as in POP3) and then wonder why it ... Exchange can inform and enforce quotas on mail storage. ... Server side rules? ...
      (microsoft.public.exchange.design)
    • Re: exchange basics
      ... If you find users switching between client ... > store, so you're right, it wouldn't be a big deal. ... >> -If messages can be stored on server instead of downloading, ... > Exchange can inform and enforce quotas on mail storage. ...
      (microsoft.public.exchange.design)
    • Re: WM5, VPN via PPTP/MPPE, and direct connection to Exchange
      ... non-Microsoft VPN server, in order to access an Exchange Server on a private ... clients to Exchange via the VPN server, I have to select the the Outlook ... NOT synchronising with a client laptop. ...
      (microsoft.public.pocketpc.phone_edition)
    • Re: One user having messages stuck in Local Delivery
      ... so you won't have any effect to the client PCs. ... migration of the Exchange data, ... brand spanky new intel rackmount server which has only been sitting here ... tomorrow morning another mailbox or two will start failing. ...
      (microsoft.public.windows.server.sbs)
    • Re: Two email domains
      ... The client decided to order new server. ... You can take them from a barely functioning SBS to fully functional ... HQ may or may not be storing data in Exchange regardless ...
      (microsoft.public.windows.server.sbs)