[cisco-voip] 1760 as a IPIPGW (CUBE)

[Tanner Ezell]

Well that's a bit discouraging, as I surely cannot afford a 2800 series or
better router in my lab =(

On Sun, Apr 5, 2009 at 9:45 AM, Nick Matthews <matthn at gmail.com> wrote:

> While the 2600 supports CUBE, it won't have 12.4(20)T support.  I say
> this as a fair warning because there are a number of SIP/CUBE
> situations that require 12.4(20)T.
>
>
> -nick
>
> On Sun, Apr 5, 2009 at 12:34 PM, Tanner Ezell <tanner.ezell at gmail.com>
> wrote:
> > That was my thought, I noticed it was not listed as compatible but some
> of the commands were available. Ill have to see about getting a 2610XM or so
> > ------Original Message------
> > From: Nick Matthews
> > Sender: matthn at gmail.com
> > To: Tanner Ezell
> > Cc: VOIP Group
> > Subject: Re: [cisco-voip] 1760 as a IPIPGW (CUBE)
> > Sent: Apr 5, 2009 9:21 AM
> >
> > You can accomplish something very close to CUBE, but no, it will not
> > be a CUBE.  There isn't any IPIPGW code for the 1760.
> >
> > The commands exist in non CUBE software packages, but there is a
> > slight variation in many of the corner case scenarios that makes it
> > work more like a SBC instead of a terminating gateway.  The commands
> > 'allow-connections h323-to-h323' and such have been around for
> > CUBE-like scenarios like routing calls between two CMEs to CUE
> > (SIP-H323).  This behavior is different from actual IPIPGW
> > implementation.
> >
> > As well, there were large improvements in CUBE in 12.4(20)T,
> > especially with SIP.  If you're doing SIP at all 12.4(20)T is a good
> > place to start at, and since the 1760 is being phased out, 12.4(15)T
> > is the last release for that platform.
> >
> > Short story - it's not a CUBE capable router, but you may get lucky
> > and have it work if you're dealing with the simple standard-case
> > situations (not supplementary services).
> >
> >
> > -nick
> >
> > On Sat, Apr 4, 2009 at 10:44 PM, Tanner Ezell <tanner.ezell at gmail.com>
> wrote:
> >> I've been toying with a 1760, trying to get it to act as an IP to IP
> Gateway
> >> with limited success, calls come in as h323, but I never see any attempt
> to
> >> go out as SIP. I am beginning to wonder if the device is even capable.
> >> _______________________________________________
> >> cisco-voip mailing list
> >> cisco-voip at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>
> >>
> >
> >
> > Sent via BlackBerry from T-Mobile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090405/73b3b6c6/attachment.html>