Download
Share
Print this page
  1. Manuals
  2. Brands
  3. VegaStream Manuals
  4. Software
  5. Vega Gateway
  6. Engineer's manual

VegaStream Vega Gateway Engineer's Manual

Polycom manual vega gateway
Hide thumbs

Advertisement

Quick Links

Download this manual
This guide has been written to assist the pre-sales engineers of VegaStream's distributors and
their resellers.
The guide details a set of standard configurations along with key considerations and
rd
recommended 3
A guide to the scenarios and information you will find within this document are listed below.
1.
VoIP between sites
2.
VoIP between sites and home-worker / remote office
3.
VoIP between sites and home-worker / remote office using a proxy
4.
Analog long line extensions
5.
IP Telephony
6.
PSTN toll bypass
7.
TDM to / from VoIP converter
8.
Leased line eliminator for QSIG connections between sites
9.
Analog connections
- Analog Applications
a)
Vega FXS for analog telephones
b)
Analog breakout to the PSTN – e.g. for a company or for a PSTN toll bypass
c)
FXS connection to a PBX
d)
FXO connection to a PBX
e)
PBX to PBX connectivity – using both FXS and FXO
f)
PBX to PBX connectivity – using FXS only
g)
PBX to PBX connectivity – using FXO only
h)
Mass analog connection – using a Vega 400 and a channel bank
i)
Analog long line extensions
Appendix 1 - 3
Appendix 2 - Things to consider
Version 2.1
Vega Gateway Scenarios.
deploying them, especially the functionality of devices not designed and delivered by VegaStream.
VoIPon Solutions www.voipon.co.uk sales@voipon.co.uk Tel: +44 (0) 1245 600560
Vega Gateway
Scenarios
A Pre-sales Engineer's
guide
party interoperable products.
rd
Party Products
16 March 2006
Examples are given in best faith – ensure that you check the capabilities of systems before
Page 1 of 33
©2005-2006 VegaStream Ltd.

Advertisement

loading
Need help?

Need help?

Do you have a question about the Vega Gateway and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for VegaStream Vega Gateway

  • Page 1 Appendix 2 - Things to consider Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 2 IP network. All other calls from the PBX continue to be routed to the PSTN. All calls from the PSTN are routed to the PBX. The source Vega gateway will direct the VoIP calls to specific destination gateways, based on the telephone number dialled (single numbers or number ranges can be groomed off to specific destinations).
  • Page 3 IP connection is down. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 4 • For NAT traversal between sites, consider SNOM NAT filter, SIParator or Alcatel T610 Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 5 IP network. All other calls from the PBX continue to be routed to the PSTN. All calls from the PSTN are routed to the PBX. The source Vega gateway will direct the VoIP calls to specific destination gateways, based on the telephone number dialled (single numbers or number ranges can be groomed off to specific destinations).
  • Page 6 PBX towards the PSTN. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 7 • For NAT traversal between sites, consider SNOM NAT filter, SIParator or Alcatel T610 Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 8 By inserting a Vega gateway between the PSTN and the PBX the Vega can consider how to handle every call between the PSTN and the PBX either routing the call over IP, routing the call to the PBX or routing the call to the PSTN.
  • Page 9 (as the PBX will expand this to a full number before presenting it to the PSTN). Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 10 • Home-workers will be able to dial extension numbers of any of the PBXs (as the proxy will resolve the phone number and route the call to the appropriate Vega gateway). Calls made to users on a PBX will appear to the PBX to come from the PSTN and so will not provide the advanced functionality to the home-worker that an extension user would have (e.g.
  • Page 11 • SNOM, Mitel MKC, IVR technologies, NetSapiens Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 12 2 FXO ports (can be used Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 13 • For VPN at home site consider Alcatel T610 Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 14 • IP handsets or soft phones may also be used Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 15 • Intelligent Call Routing: Rostrvm, Teleware, Alceo, Interactive intelligence Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 16 If credit runs out during a call then the call can be torn down (terminated). Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 17 • IVR technologies • Tangerine Inc Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 18 The Vega gateway connects to the E1, T1 or BRI interface of the existing equipment and can receive calls and convert them to SIP or H.323; the Vega gateway can also receive SIP or H.323 calls and convert them to E1, T1 or BRI calls.
  • Page 19 • - Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream. VoIPon Solutions www.voipon.co.uk sales@voipon.co.uk Tel: +44 (0) 1245 600560 16 March 2006 ©2005-2006 VegaStream Ltd.
  • Page 20 E1 interfaces – then, using the destination information in the QSIG header the Vega can select the correct far end Vega gateway to send the ‘tunnelled’ QSIG data to. The far end gateway unpacks the received ‘tunnelled’ QSIG messages and presents them on its T1 or E1 interface.
  • Page 21 ‘point-to-point trunking’ means that all calls on a specific Vega trunk will be routed to a specific destination trunk on a specific destination Vega gateway ‘fully meshed’ indicates that on a call by call basis the Vega gateway can select the appropriate IP endpoint to send the QSIG data to.

  • Page 22: Analog Connections

    Vega 50 FXO supports Belcore sdmf and mdf standards, SPA-2000 support these and many others Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 23 • Caller ID is only supplied in sdmf or mdmf formats on the Vega 50 FXS (our range of home gateways support more formats). Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 24 600R operation. 900R impedance is also available. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 25 Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 26 • Enable disconnect supervision on FXO / PBX interface if possible. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 27 • Need disconnect supervision on at least 1 Vega – preferably both. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 28 See “1 VoIP between sites” above. Version 2.1 Vega Gateway Scenarios. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 29 Version 2.1 16 March 2006 Page 29 of 33 Vega Gateway Scenarios. ©2005-2006 VegaStream Ltd. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 30 Version 2.1 16 March 2006 Page 30 of 33 Vega Gateway Scenarios. ©2005-2006 VegaStream Ltd. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 31 Version 2.1 16 March 2006 Page 31 of 33 Vega Gateway Scenarios. ©2005-2006 VegaStream Ltd. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.
  • Page 32 Version 2.1 16 March 2006 Page 32 of 33 Vega Gateway Scenarios. ©2005-2006 VegaStream Ltd. Examples are given in best faith – ensure that you check the capabilities of systems before deploying them, especially the functionality of devices not designed and delivered by VegaStream.

  • Page 33: Appendix 2 - Things To Consider

    11. Appendix 2 – Things to consider Audio quality • Ensure that the IP network does not drop data • Use QOS to ensure that VoIP traffic is given priority through routers • Choose best quality codec that is possible for the bandwidth available •...

This manual is also suitable for:

Vega gateway scenarios