Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <4c1b8abe.40...@redhat.com>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <48000>
Message-ID:
The method you have described sets up a trunk between sipX
and CCM/CUCM, so the medi
sipXecs - so easy...
even a Senior Communications Engineer at Red Hat can do it...
Doesn't quite have the same ring...
This message and any files transmitted with it are intended only for the
individual(s) or entity named. If you are not the intended individual(s) or
entity named you are hereby
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 t
-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
