Hi Damien, running through this thread i come to think: 1.) keeping H323 and adding SIP is the best to do as both will be present in the future VoIP world 2.) relying on FWD is bad, we could and should use E164.org and E164.arpa for unified numbers, those are the official ones. Adding a FWD account on top of seconix is a "nice to have", but nothing more. 3.) making ILS be completely removed is a controversial issue, as i'm not fully sure what professionals use it for with NetMeeting. We definitely need a Win32 fully fledged GM (or have a more popular OpenPhone/MyPhone) before making this step. 4.) we should keep in mind that SIP shall be passing new NAT technology easily within a hopefully decent amount of time. 5.) while all this discussion about how to technically ease things is going on.. has anybody looked into S/RTP or any SSL/TLS security for VoIP again? Have you been considering using TLS connections for the new LDAP? I think we should do that as passwords are by all means protection worthy. 6.) choosing multiple gatekeepers/gateways should be used like the Email identities in you MUA. I.e. you can just choose while clicking "call" which identity to use (and thus which provider as gateway). -- Best regards, Kilian
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil