Sweet!....thats what I was hoping to hear. I didn't think Avaya has released any code for it's new openscs project as the website still has nothing new from June. But was wondering if I missed something if Avaya had actually released openscs code.
I do think its funny the openscs webpage notes that "As of July Avaya no longer participates in SIPFoundry.SIPFoundry has forked the code base and is being maintained by a newstartup company." Rather than Avaya being the one that forked it into a new openscs project ;-) -M >>> Joegen Baclor <[email protected]> 09/16/10 10:00 AM >>> Hi Matt, I've heard that Avaya is trying to solve this as well. But this one iscompletely community/ezuce code. Joegen On Thursday, 16 September, 2010 09:04 PM, Matt White wrote: Great news. This will go a long way towards increased interop. Out of curiosity, is any of this based on the work that avaya was doingbefore the fork? Or is this 100% community/ezuce code? -M >>> Joegen Baclor <[email protected]> 09/16/10 4:37 AM>>> Hi Folks, I just thought you'd be interested in knowing that I have already successfully sent a call to port 5060 and forwarded to the bridge by redirection. See attached log from twinkle. Unfortutely, I am behind a firewall controlled by the ITSP so this is not yet tested in anactual environment. If you take a look at the log I have attached, the 200 OK is now coming from sipXbridge event if the call passed through the main sipXproxy listener. The ACK in this case will be misrouted because sipXbridge is sending the external IP as its contact. This however should not be an issue if the actual test call came from an entity outside my firewall. Hopefully we will have some more good news in the days to come. Joegen http://list.sipfoundry.org/archive/sipx-dev/ </[email protected]>
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
