-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hiya Tony, On 09/01/2010 04:23 PM, Tony Graziano wrote: > If sipx is going to produce the configuration files, there are a > couple of "have-to's" (IMO) that need to be in place in order for it > to be successful. > > 1. Interop testing, to ensure it handles MOH, transfer, and other call > flow scenario's without anything serious or needing attention. This > also helps to learn/define what should be the "safe defaults" for the > configuration produced by sipx. > > 2. Support for SRV records. The year is 2010, not 2001. At some point > it makes total sense to start embracing something that should have > been adopted "years ago". Imagine getting the phones, having them > work, then doing HA and finding out they are "worthless" for that > function... I honestly have no idea if they support SRV's rather than direct IP/FQDN connections... I will have a look and report back. > 3. sipx needs to start provisioning over http/https, this is not > limited to yealink phones. Polycom phones can benefit from this as > well and others too. That's a big job. > > 4. Does yealink provision over ftp/tftp now? If so, the list of > "have-to's" gets smaller. The Yealink's provision over HTTP(S)/FTP/TFTP :-) - -- Gavin Spurgeon. AKA Da Geek - ---------------------------------------------------------------------- "The happiest of people don't necessarily have the best of everything, they just make the most of everything that comes along their way.." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkx+cugACgkQvp6arS3vDiq9CgCdHIIwebf9dwfLyqr9VzLBA3ax yvIAnjF5G15gnaJ4frZyV0StH32isHlM =wE0M -----END PGP SIGNATURE----- -- This message was scanned by DaGeek Spam Filter and is believed to be clean. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
