[cisco-voip] SRST design Q

[Tired Banchini]

Guys,

Is this the right forum for this type of question ?

On Tue, Aug 18, 2009 at 12:37 AM, Tired Banchini <
tired.banchini at googlemail.com> wrote:

> hi chaps,
>
> I am still on the early stages of the learning curve for voip so pls bear
> with me. In regards to setting up SRST, I have read many docs but I am still
> a little unclear on some design aspects, I was hoping some experienced hands
> can share some knowledge.
>
> First basic question is, can SRST work when the local 'branch' router is
> either a VOIP GW or a regular transit router?
>
> If yes and the router is a transit router will bear bones SRST where PSTN
> is also directly connected to SRST router, what is best/ norm practice in
> terms of when users want to make calls to the PSTN when in fallback mode
> i.e. what number are presented to PSTN and also how are inbound calls
> treated?
>
> I am thinking about a scenario where you have a DDI ranges presented at
> remote PSTN hub sites that covers the remote site running SRST. So from PSTN
> perspective all numbers with lets say 1xxx would route via the hubs and the
> SRST site is 12xx. In the scenario where WAN is down at remote, my
> understanding of SRST is that the same DNs will register will the local SRST
> router i.e. the 12xx... However, I am assuming the PSTN attached to the SRST
> router is another provider with a different DDI, does this simply mean I
> have to do some translations to use PSTN?
>
> Also on the same sort of subject ! When integrating sites in a CUCM
> clusters, trying to get some concrete reasons for not configuring the sites
> with CME and running them as GWs to the cluster versus registering the sites
> directly with one of the closest clusters; is there any scientific rules for
> how far latency wise the cluster should be from end user phones ?
>
> thnks in advance
> TB
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090819/289a271e/attachment.html>