Wonderful, I will discuss this ACME config with their engineer later today..
Also, what needs to be done on SIPX to force the registration through the external ACME SBC? What I did for that was, under the line registration form I changed the outbound proxy and the Primary registration server to point to the SBC and this worked perfectly .. I assume this is correct? Unmanaged GW is what we have currently in use by SIPX with no default SBC address assigned for internet calling (as this didn't make any changes when added). Regards Saad On Fri, Mar 16, 2012 at 9:27 AM, Joe Micciche <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03/16/2012 07:11 AM, [email protected] wrote: > > I agree with Emilio, Acme is one of the top products on the > > market. > > > > Maybe somebody with a properly working Acme could document it in > > the Wiki for those who follow... > > > > http://wiki.sipfoundry.org/display/sipXecs/Acme+Packet+SBC+sample+config+for+Remote+Workers > > Not 100% complete as noted on the page; but once you get the Acme > Packet config nailed, they work beautifully. > > - -- > ================================================================== > Joe Micciche [email protected] > Red Hat, Inc. http://www.redhat.com > Senior Communications Engineer X (81) 44554 > +1.919.754.4554 Key: 65F90FE1 > ================================================================== > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk9jP9AACgkQJHjEUGX5D+GzygCgt7zrgsseBxxVZ6z6ORlVsiHy > +bcAn2fOUrur208FOiAhLDDw4YiKdCFN > =vyL/ > -----END PGP SIGNATURE----- > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
