|
Home > Archive > Voice over IP Cisco > May 2005 > Remote Callmanager on SAT link
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Remote Callmanager on SAT link
|
|
| Trey Howland 2005-05-17, 5:45 pm |
| I have a customer who requires their PRI or T1 CAS circuit to be terminated on
the remote end. I'm looking for a solution for extending this across a IP
satellite link? Anyone have experience or pointers?
Thanks,
Trey
--
Georgia Institute of Technology Atlanta, Georgia
Georgia Tech Research Institute
Electronic Systems Laboratory
Public Key ID: 0x894F4419
[7338 D848 8BEE FF6D 23D1 4355 2F6C DE0C 894F 4419]
| |
| Wes Sisk 2005-05-17, 5:45 pm |
| Hi Trey,
GT CMPE grad in 1999. You can put an h323 gateway or MGCP gateway over
a satellinte hop away from CM. I would recommned using h323 so the call
routing logic stays on the router and keepalives are not constantly
exchanged beteen CM and the gateway. Additinally, MGCP uses UDP. Is
your link proned to drops? If you choose to go MGCP, you can use h323
fallback so when the gw looses IP connectivity to CM, it operates in
h323 mode.
/Wes
Trey Howland wrote:
>I have a customer who requires their PRI or T1 CAS circuit to be terminated on
>the remote end. I'm looking for a solution for extending this across a IP
>satellite link? Anyone have experience or pointers?
>
>Thanks,
>Trey
>
>
>
| |
| Trey Howland 2005-05-21, 5:45 pm |
| Thanks for the response. I need the PRI to extend across the sat link
to support legacy tactical PBX's. The router would possibly be
connected to that PBX on a t1 card. So I'm looking at something
similar to a Shout 900
[http://www.net.com/products/products_shoutip.shtml]. Is there
something in the cisco line that provides a similar function?
Trey
On May 17, 2005, at 10:23 AM, Wes Sisk wrote:
[vbcol=seagreen]
> Hi Trey,
>
> GT CMPE grad in 1999. You can put an h323 gateway or MGCP gateway
> over a satellinte hop away from CM. I would recommned using h323 so
> the call routing logic stays on the router and keepalives are not
> constantly exchanged beteen CM and the gateway. Additinally, MGCP
> uses UDP. Is your link proned to drops? If you choose to go MGCP,
> you can use h323 fallback so when the gw looses IP connectivity to CM,
> it operates in h323 mode.
>
> /Wes
>
> Trey Howland wrote:
>
Georgia Institute of Technology Atlanta, Georgia
Georgia Tech Research Institute
Electronic Systems Laboratory
Public Key ID: 0x894F4419
[7338 D848 8BEE FF6D 23D1 4355 2F6C DE0C 894F 4419]
| |
| Wes Sisk 2005-05-21, 8:45 pm |
| A cisco 1760V router with vwic-1mft-t1 should do nicely.
One thing i forgot to mention - doing h323 over any high latency link
there is good chance for delayed audio cut through. You're looking at
about 10 TCP packets in each direction (give or take for fragementation,
fast start, etc). So you will see audio cut through delayed by
~10*(latency). This is a simple rough estimate.
/Wes
Trey Howland wrote:
> Thanks for the response. I need the PRI to extend across the sat link
> to support legacy tactical PBX's. The router would possibly be
> connected to that PBX on a t1 card. So I'm looking at something
> similar to a Shout 900
> [http://www.net.com/products/products_shoutip.shtml]. Is there
> something in the cisco line that provides a similar function?
>
> Trey
>
>
> On May 17, 2005, at 10:23 AM, Wes Sisk wrote:
>
> Georgia Institute of Technology Atlanta, Georgia
> Georgia Tech Research Institute
> Electronic Systems Laboratory
>
> Public Key ID: 0x894F4419
> [7338 D848 8BEE FF6D 23D1 4355 2F6C DE0C 894F 4419]
|
|
|
|
|