Centralized CM, remote sites.  MGCP has proven too problematic /
unreliable, so I'm trying to migrate to H.323 only.

We have overhead ringers connected to FXS ports on 2821/2851 routers;
dial the DN, and the device starts to ring.  What we do is call forward
the main number to the DN of the ringer, so that if the receptionist is
away, anyone can pickup with the Group Pickup button when they hear the
overhead ringer.

All of this works if we use MGCP for the analog ports.

Is there any way to do this with H.323?

[ Post a follow-up to this message ]

Sure.

Create a route-pattern on CCM with that DN, point it at the H.323 gateway

On the gateway, create a dial-peer with that destination-pattern pointing to
that port...



Jonathan

On 3/23/07, Robert Kulagowski <bob@smalltime.com> wrote:
>
> Centralized CM, remote sites.  MGCP has proven too problematic /
> unreliable, so I'm trying to migrate to H.323 only.
>
> We have overhead ringers connected to FXS ports on 2821/2851 routers;
> dial the DN, and the device starts to ring.  What we do is call forward
> the main number to the DN of the ringer, so that if the receptionist is
> away, anyone can pickup with the Group Pickup button when they hear the
> overhead ringer.
>
> All of this works if we use MGCP for the analog ports.
>
> Is there any way to do this with H.323?
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

Jonathan Charles wrote:
> Sure.
>
> Create a route-pattern on CCM with that DN, point it at the H.323 gateway
>
> On the gateway, create a dial-peer with that destination-pattern
> pointing to that port...

That part worked (we had it working before), but how do I make it part
of the call pickup group?

I've tried:

1)  Putting a *71 line appearance on a phone, but I don't get a
simultaneous ring on the phone and on the H.323 FXS port.
2)  Putting in a "virtual" DN in a CTI port, but that doesn't work either.

[ Post a follow-up to this message ]

I don't think there's any way to make that work.  If MGCP won't work for
you, an ATA 186 might be your best bet.



On 3/23/07, Robert Kulagowski <bob@smalltime.com> wrote:
>
> Jonathan Charles wrote: 
>
> That part worked (we had it working before), but how do I make it part
> of the call pickup group?
>
> I've tried:
>
> 1)  Putting a *71 line appearance on a phone, but I don't get a
> simultaneous ring on the phone and on the H.323 FXS port.
> 2)  Putting in a "virtual" DN in a CTI port, but that doesn't work either.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>



--
kris seraphine

[ Post a follow-up to this message ]

Kris Seraphine wrote:
> I don't think there's any way to make that work.  If MGCP won't work for
> you, an ATA 186 might be your best bet.

TAC just confirmed the same thing, so it looks like I'm going to have to
spend $250 list per site to get the piece of mind that comes with
getting rid of MGCP.

[ Post a follow-up to this message ]

Exactly what problems are you having with MGCP and FXS?  I have the same
type of thing (MGCP FXS for night bells) deployed a few places and never had
a nyproblem.

On 3/28/07, Robert Kulagowski <bob@smalltime.com> wrote:
>
> Kris Seraphine wrote: 
>
> TAC just confirmed the same thing, so it looks like I'm going to have to
> spend $250 list per site to get the piece of mind that comes with
> getting rid of MGCP.
>



--
kris seraphine

[ Post a follow-up to this message ]

Kris Seraphine wrote:
> Exactly what problems are you having with MGCP and FXS?  I have the same
> type of thing (MGCP FXS for night bells) deployed a few places and never
> had a nyproblem.

MGCP ports on remote site routers unregistering with CM thereby breaking
faxing.  MGCP process as a whole dying, and having to do a no mgcp /
mgcp on the router to restore functionality.

The routers are already configured for H.323 for call preservation into
and out of SRST mode, so having a solution to the call pickup group was
the only thing keeping us with MGCP.  And since I had an ATA-188 handy,
it took about 3 minutes to confirm that it worked, and it did.

[ Post a follow-up to this message ]

I would dedicate my resources to getting the service provider to fix the WAN
problem

On 3/28/07, Robert Kulagowski <bob@smalltime.com> wrote:
>
> Kris Seraphine wrote: 
>
> MGCP ports on remote site routers unregistering with CM thereby breaking
> faxing.  MGCP process as a whole dying, and having to do a no mgcp /
> mgcp on the router to restore functionality.
>
> The routers are already configured for H.323 for call preservation into
> and out of SRST mode, so having a solution to the call pickup group was
> the only thing keeping us with MGCP.  And since I had an ATA-188 handy,
> it took about 3 minutes to confirm that it worked, and it did.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]