There ya go... The call trace would have shown you connecting with a different codec. If you don't have g.729 licenses I'd turn that off too, because that might be problematic too. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431
Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Sent: Thu Oct 14 02:36:50 2010 Subject: Re: [sipx-users] conference bridge transfer unsuccessful with voip.ms [SOLVED] On 10/13/2010 08:17 PM, Joe Conway wrote: > On 10/13/2010 07:39 PM, Tony Graziano wrote: >> >> Make sure your voip.ms <http://voip.ms> account is set for: >> >> NAT (Network Address Translation) [no] > > I tried that, and it doesn't make any difference. Internal extension > transfers work, conference bridge no so much (the attendant says "please > wait while I transfer your call", but then nothing) :-( > > Yet everything works perfectly with sipgate. I guess I need to do a sip > trace to see what is going on... For the archives, as it turns out, I had changed the allowed codecs on my voip.ms account from the default/recommended (G.711U and G.729a) to "Allow All". When I changed this back to the recommended codecs, the conference bridge started working again (or possibly it was working all along, but I could not hear it?). Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
