[cisco-voip] VG224 configuration

[Nick Matthews]

check out the data sheet:
http://www.cisco.com/c/en/us/products/collateral/unified-communications/iad2430-integrated-access-device/product_data_sheet09186a008019aded.html

-nick



On Fri, Apr 4, 2014 at 2:21 PM, Sivakumar Donthamchetty <
siva at dateksystems.com> wrote:

> Hi Nick,
>
>
>
> Thank you for the info.
>
>
>
> Wanted to confirm that IAD series will be able to convert the IP calls
> that are getting into the IAD and pass it to the FXS so that I can plug-in
> the FXS to my PBX Analog trunks.
>
>
>
> Regards
>
> Siva
>
>
>
> *From:* matthn at gmail.com [mailto:matthn at gmail.com] *On Behalf Of *Nick
> Matthews
> *Sent:* Friday, April 04, 2014 6:40 AM
> *To:* siva at dateksystems.com
> *Cc:* Tim Smith; cisco-voip at puck.nether.net Group
>
> *Subject:* Re: [cisco-voip] VG224 configuration
>
>
>
> The IAD series of boxes are very popular for this sort of thing, they are
> architecturally similar to the VG224.
>
> -nick
>
>
>
> On Thu, Apr 3, 2014 at 2:08 PM, Sivakumar Donthamchetty <
> siva at dateksystems.com> wrote:
>
> Hi Tim,
>
>
>
> Thank you for the info. Yes, I got to learn that they are typical for CUCM
> and CME. But, someone mentioned it can be used for any IPàAnalog calls.
>
>
>
> And yes, the PBX has FXO card or Trunk Side analog lines, which I am
> planning to plug-in to.
>
>
>
> My scenario is I want my PBX incomming Analog lines to SIP lines. So I
> thought any GW which can take SIP calls and pass as analog will do it.
>
>
>
>
>
> Regards
>
> Siva
>
>
>
> *From:* Tim Smith [mailto:tim.smith at enject.com.au]
> *Sent:* Wednesday, April 02, 2014 4:40 PM
> *To:* siva at dateksystems.com; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] VG224 configuration
>
>
>
> Hi,
>
>
>
> In theory, you could probably make this work, but I think it would be
> considered an unusual application for these boxes.
>
> Their typical application is to provide analog connectivity for endpoints
> (i.e. modems, faxes, analog handsets) into a Cisco IPT environment, i.e.
> typical CUCM or CME call control.
>
>
>
> The ports are FXS so you would need FXO interfaces on your PBX (you have
> limited features available here compared to ISDN for example)
>
> You can send and receive calls via SIP to the VG224 (they can also run
> MGCP, SCCP and H323)
>
> Normally you would be sending and receiving calls to and from a CUCM for
> example
>
>
>
> Just search cisco.com and cisco.com support forums and you should find
> sample configs. Probably best to have a crack at it first, then post your
> findings and any further questions.
>
>
>
> If you provide more background, there is likely a better solution. (Just
> because we can make something work, doesn't mean we should do it in
> production)
>
> In general I would think a typical ISR router 29XX / 39XX would probably
> be more suitable (and flexible)
>
> And something like ISDN would be nicer for connecting two systems
>
>
>
> Cheers,
>
>
>
> Tim
>
>
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Sivakumar Donthamchetty
> *Sent:* Thursday, 3 April 2014 9:50 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] VG224 configuration
>
>
>
> Hi All,
>
>
>
> Wanted to check first of all if I can use VG224 for converting SIP calls
> to analog so that I can connect the Analog interface to a PBX.
>
>
>
> If so, can some one send me a sample configuration.
>
>
>
> Also, does the image file on the GW matters or any image should work?
>
>
>
> Regards
>
> Siva
>
>
>
> *Datek Systems Inc. DBA VoipXchange, Inc.*
>
> *240 E. Gish Rd.*
>
> *San Jose, CA. 95112*
>
> *PH: (408) 200-7820 <%28408%29%20200-7820>*
>
> *FX: (408) 451-9307 <%28408%29%20451-9307>*
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140406/5a48fbe3/attachment.html>