Many of you know that there are two versions of the new Avaya J series phones. There is the IP Office version and the OPEN SIP version designed to break into the Polycom dominated space. Has anyone tested the J179 Open Sip phone with Freepbx? If so, what works and what doesn't work. TIA
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
J179 and FreePBX
- Thread starter Icarealot
- Start date
It's certified on Broadsoft. I presume Broadsoft has some adoption of config files so if I make your line a type 'polycom' it might spit out a polycom styled configuration for your set. Same idea with Freepbx.
Now, nothing ever stopped you from using Avaya's 46xxsettings file and disabling support for specific Avaya environments and just use it as a SIP Simple device. Now though, in the newer firmwares for 96x1SIP and J1x9, you can say 'get $yourmacaddr.txt and that file is unique per device and it can set SET SIP USERNAME and PASSWORD to make provisioning simpler.
I guess you'd have to get it registered and test out the features you use with a FreePBX and see how well it supports it.
Now, nothing ever stopped you from using Avaya's 46xxsettings file and disabling support for specific Avaya environments and just use it as a SIP Simple device. Now though, in the newer firmwares for 96x1SIP and J1x9, you can say 'get $yourmacaddr.txt and that file is unique per device and it can set SET SIP USERNAME and PASSWORD to make provisioning simpler.
I guess you'd have to get it registered and test out the features you use with a FreePBX and see how well it supports it.
- Thread starter
- #3
Thank You Kyle. The phone was designed for use in Broadsoft environment. Pricing is excellent and the phone is small. I'm asking one of my suppliers to test the J179 with a Grandstream system and see if it functions properly. This supplier sells both solutions.
I'm sure it can, I would think it's more a function of to what extent your open SIP server supports spitting out a config file specific to the vendor's device - specifically Avaya in this case.
I don't know if you're the Grandstream guy, or what kind of development is needed to make a central system like that spit out a global 46xxsettings.txt that has some config as well as "GET $YOURMACADDR.TXT" and a specific MACADDR.txt, but that'll be the bigger hurdle in having easy peasy provisioning. I'd like to think that by definition, if 3 switches are 'OPEN SIP' compliant, that I'd be able to get most of the features to work the same across them. But, that's implying SIP has a standard!
I don't know if you're the Grandstream guy, or what kind of development is needed to make a central system like that spit out a global 46xxsettings.txt that has some config as well as "GET $YOURMACADDR.TXT" and a specific MACADDR.txt, but that'll be the bigger hurdle in having easy peasy provisioning. I'd like to think that by definition, if 3 switches are 'OPEN SIP' compliant, that I'd be able to get most of the features to work the same across them. But, that's implying SIP has a standard!
- Status
