It's pretty trivial/non-invasive to add a SIP trunk to CCM, even back with 4.1 which is what we're running. If you want screenshots, let me know and I can grab a few of the config screens for you. -- Nathan On 04/25/2013 04:43 PM, Lesley Pervis wrote:
Well, the CCM is a customer's, and they've got it running SCCP, but not SIP. Since it looks like FS can't act as an SCCP client, I'm thinking they're either going to have to do as you say, add SIP, or we'll have to hack together some ugly SIP<->analog<->SCCP thing together with ATAs.
On Thu, Apr 25, 2013 at 3:29 PM, Nathan Neulinger <nneul@mst.edu <mailto:nneul@mst.edu>> wrote:
What version of CCM are you running, unless it's truly ancient - it should support SIP.
That's how I'm using FS right now.
PSTN -> CCM -sip-> FS -> SIP + Skinny phones
with eventual intent of flip-flopping CCM and FS in that picture.
-- Nathan
On 04/25/2013 03:48 PM, Lesley Pervis wrote:
Hi all,
I've been looking around, and I'm pretty sure it's not possible, but I thought I'd check here.
mod_skinny seems to be written to allow SCCP devices to register with FS, and FS acts as a CallManager replacement
However, I'm wondering if it's possible to configure FS to act as an SCCP client. I want to set up something similar to a Sofia profile gateway that, instead of registering with a SIP server, registers with CallManager so that FS can bridge calls between SIP devices and the SCCP-only CallManager.
Thanks for any info, Les
-- ------------------------------__------------------------------ Nathan Neulinger nneul@mst.edu <mailto:nneul@mst.edu> Missouri S&T Information Technology (573) 612-1412 <tel:%28573%29%20612-1412> System Administrator - Architect
-- ------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect