On 6/18/2010 11:03 AM, Joe Micciche wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I did some searching and came up empty on integrating/trunking sipXecs
> and Cisco Call Manager, so I thought I'd post this to the list for
> others who may search for a solution. My interest in doing this is so we
> can seamlessly pass calls between the two, and leverage our PSTN
> gateways around the world.
>
> It's *surprisingly* easy, and errors passing calls between the 2, in my
> case, were due to a dial plan permissions problem on sipXecs.
>
> On the sipXecs side:
> 1. Select Devices ->  Gateways ->  SIP Trunk from the drop-down.
> 2. Check Enabled; give it a name; enter the IP or FQDN of CCM; port 5060
> (if this is what you use on CCM); set your Transport to match the CCM
> SIP Trunk transport; then set Location, Shared, and provide a description.
>       This can be duplicated if you have multiple Subscribers; or FQDN
> changed if you have SRV set up for your cluster(s).
>
> On CCM:
> 1. Select Device ->  Trunk ->  Add New, select SIP Trunk.
> 2. Create a new Non-secure SIP trunk using the FQDN or IP of sipXecs.
> It's a very generic trunk, CCM admins should know all settings.
>
> Obviously you have to set dial plan and permissions on the sipXecs: for
> the time being, I have chosen to pass all PSTN calls to CCM rather than
> gateways b/c we have PSTN access and LCR/TEHO set up already on CCM, no
> need to duplicate it. This gives endpoints on sipXecs access to our
> internal dial plan; and vice versa. Also, route patterns (or
> translations, or whatever you prefer) need to be set on CCM to pass
> calls to sipXecs. I've not set any security on this yet, still mulling
> that over.
>
> - -- 
> ==================================================================
> 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 v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkwbir4ACgkQJHjEUGX5D+E4wQCgm20KgF4D1OXyOhf/Rp1OV6HP
> y2wAn2Y8F4sGv1tqr4NCa0CvimG+nf/t
> =15jI
> -----END PGP SIGNATURE-----
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
>    
One more shot... Sorry
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to