Specific question (and some answers) can be better found through the sipx-dev list. Development versions are not always stable, and there are always minor issues, sometimes major, which is why you should never use this in a working environment.
Have you tried a 3.11.x ISO? I've yummed a couple of 3.10 installed from ISO to a dev version to check things out, but not for a few weeks. If you look is sipx-dev lists, you'll get an idea of this, I think Ranga posted today he was having sipxconfig issues with the latest build. Once you get to a 3.11 version that gives you what you want, you probably want to disable your repo while you do testing. Realize 3.11 is the dev testbed for 4.0, which is not slated until sometime toward the end of the 1st quarter 2009, so it's got a lot of sprint work going into it still. Sprints mean changes, changes sometimes break things. You might be better trying 3.11.4 ISO, but might have to do manual config for some of sipxbridge until you know yum will not break anything. Realize also that sipxbridge is only partly finished. The bridge has 3 main goals as I understand it: 1. Connect to ITSP's (done, but still being tweaked). 2. Allow remote registrations through NAT (not done yet). 3. Be configurable/manageable via sipxconfig (just started to show in dev, being cleaned up). If you need production stability and trunking, i highly recommend an Ingate unless you can wait a few months. >>> "Dean Hiller" <[EMAIL PROTECTED]> 09/26/08 17:40 PM >>> man, 3.11 is tough to get working. I keep trying to reclean the original sipx dropping db and following the wiki rpm -qa.... command as well as deleting all leftover sipx folders as I am trying to do a complete clean. I finally whacked just about everything and then I was getting an error about missing file.....httpd-sipxchange-common-ssl.conf which for some reason was there but with a .in extension. Once I erase the .in extension, it finds the file and complains no about invalid commands Invalid command 'nokeepalive', perhaps misspelled or defined by a module not inc luded in the server configuration anyone see this before? I am having so much trouble. I keep removing everything and reinstalling and it is not working too well. thanks for any info on this, Dean On Sat, Sep 27, 2008 at 4:17 AM, Tony Graziano <[EMAIL PROTECTED] > wrote: > >>> "Dean Hiller" <[EMAIL PROTECTED]> 09/26/08 16:02 PM >>> > it is my understanding that you have to have sipXbridge to do sip trunking > with sipx. Here are my questions > > 1. Is there not a sipXbridge that works with sipx 3.10? > > ANSWER - NO. In order to do this now you need something like an Ingate. > > 2. The yum repository for sipx 3.10 on centOS can be found on the wiki. I > did not find one for 3.11. Is there one for 3.11 to make this whole > process > easier? > > ANSWER - Change your yum repo to look at the dev branch, then update with > yum. Be aware this is not yet BETA or RC code yet, not everything will > likely work properly. It's development and should not be used for production > purposes. > > http://sipxecs.sipfoundry.org/temp/sipXecs/ > > 3. Does sipXbridge install with sipx 3.11 > > ANSWER - Yes, but using DEV means at your own risk. > > I googled "intall sipXbridge" and install sipx 3.11 to no avail :(. Can > someone help me? I have to be hooked up to a provider. > > also, when does sipx 4.0 come out? > > ANSWER - WIKI ROADMAP, FEB or MAR 09 currently. > > thanks, > Dean > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
