Categories
Gateways Products

Vega VoIP digital gateways

The Most Resilient VoIP Digital Gateways in Their Class

Vega VoIP digital gateways are small appliances that seamlessly connect your legacy telephony infrastructure, made up of PRI (T1, E1) or BRI lines, to IP networks. They are great for businesses with legacy phone equipment (such as a TDM PBX) who want to connect to SIP trunking services without having to spend money altering their current network infrastructure. They are also great for businesses that are already VoIP enabled at the core (with an IP-PBX) that need PSTN connectivity and require a SIP-to-TDM converter. Simply place the Vega VoIP Digital Gateway at the edge of your network, plug in your existing internet cable for VoIP connectivity and E1,T1 or BRI cables from your phone system and let the Vega VoIP Digital Gateway automatically handle the SIP signalling and voice media conversion for seamless voice and T.38 Fax integration.

Advanced Web GUI
Features an intuitive Quick Wizard which does all the hard work for you for new deployments. Flexible dialplan to allow you to make your own routes, including automatic failure detection with failover routing.

Diagnostic Tools
Web GUI based PCAP tracing tool to capture full signaling and media, eliminating the need to connect equipment for line tracing, fully compatible with wireshark.

Low and High Density Models
The Vega 100G and Vega 200G are our low density models with a maximum capacity for 30 and 60 SIP-TDM simultaneous calls. The Vega 400G is our high density model and the most flexible field upgradable unit for a maximum capacity of 120 simultaneous SIP-TDM calls.

E1/T1 & BRI Interface
Each E1/T1 interface (for Vega 100G, 200G, 400G) and BRI interface (Vega 50 BRI) can be independently configured as network side or terminal side. The Vega gateway can therefore be connected to a PBX or the PSTN.

Built-in Local Survivability
In the event of a WAN failure, IP phones behind the Vega gateway can continue to call each other, be routed to a backup switch or connected directly to the PSTN.

Vega VoIP Digital Gateway Models


Vega VoIP Digital Gateways are one of the most reliable fault tolerant SIP-to-TDM media Gateways on the market, sized for your business needs. All Sangoma hardware carries a one year warranty with options to extend.

Vega 50 BRI

Sangoma’s Vega 50 BRI VoIP Digital Gateways are a 2-4-8 port BRI appliance for up to 16 simultaneous BRI calls

 

  • Web GUI for configuration and troubleshooting
  • Featuring Quick Wizard for rapid d
    eployment
  • Onboard DSP for media translation
  • Interoperable with most legacy and VoIP carriers worldwide
  • Advanced flexible call routing with automatic failover and bypass routing
  • Built in Local Suitability in the case of WAN failure

Vega 100G

Sangoma’s Vega 100G VoIP Digital Gateways are a single port T1/E1/PRI appliance supporting up to 30 simultaneous calls.

 

  • Web GUI for configuration and troubleshooting
  • Featuring Quick Wizard for rapid deployment
  • Onboard DSP for media translation
  • Interoperable with most legacy and VoIP carriers worldwide
  • Advanced flexible call routing with automatic failover and bypass routing
  • Built in Local Suitability in the case of WAN failure

Vega 200G

Sangoma’s Vega 200G VoIP Digital Gateways are a dual port T1/E1/PRI appliance supporting up to 60 simultaneous calls.

 

  • Web GUI for configuration and troubleshooting
  • Featuring Quick Wizard for rapid deployment
  • Onboard DSP for media translation
  • Interoperable with most legacy and VoIP carriers worldwide
  • Advanced flexible call routing with automatic failover and bypass routing
  • Built in Local Suitability in the case of WAN failure

Vega 400G

Sangoma’s Vega 400G VoIP Digital Gateways are a quad port T1/E1/PRI supporting up to 120 simultaneous calls.

 

  • Web GUI for configuration and troubleshooting
  • Field upgradable licensing
  • Dedicated bypass ports for High availability
  • Support for Private Wire or Point-to-Point applications
  • Onboard DSP for media translation
  • Interoperable with most legacy and VoIP carriers worldwide
  • Advanced flexible call routing with automatic failover and bypass routing

For me details see Here 

Categories
Peripherals

2N IP Door Intercoms comparison chart

2N offer a range of stylish solutions for door communication. The 2N® Helios IP door and security intercoms will ensure comfort for you and your visitors and with a range of different models and feature enhancing accessories there will be an option to suit your needs.

Due to the complexity and multiple configurations possible please call or email for pricing and options.

2N® Helios IP Uni 2N® Helios IP Vario 2N® Helios IP Verso 2N® Helios IP Force 2N® Helios IP Safety 2N® Helios IP Base
Uni Vario Verso Force Safety Base
Integrated camera No Optional Optional (HD) Optional

(Standard or HD)

No yes
Buttons 1 or 2 up to 54 up to 146 1, 2 or 4 1 or 2 1 or 2
Keypad No Optional Optional Optional No No
Internal RFID card reader No Optional Optional Optional No Optional Card reader sold separately
NFC support No No Optional Optional No No NFC supported card reader and licence required
Display No Optional Optional No No No
Pictograms for visual signalling Optional No yes Optional No yes
Integrated electric switch yes yes yes yes yes yes
10W loud speaker No No No Optional Optional No
PoE yes yes yes yes yes yes
Tamper Switch yes No Optional Optional Optional yes Independent circuit control

Tamper switch sold separately

IP Rating IP54 IP53 with roof IP54 IP65/IP69K IP69K IP65 IP65 ~ on 1W speaker models

IP69 ~ on 10W speaker models

IK Rating IK10 IK07 IK08 IK10 IK10 IK07
Phone book entries 2 2000 2000 2000 2000 2000
Security Relay support yes yes yes yes yes yes Security relay sold separately
2N® Helios IP Eye & 2N® Mobile Video Support No yes yes yes No yes Only models equipped with camera
Categories
Asterisk Support Blog Design FreePBX Knowledge Base Software

G.729 Goes Royalty Free

G.729 – IMPORTANT INFORMATION

As of January 1, 2017 the patent terms of most Licensed Patents under the G.729 Consortium have expired.

With regard to the unexpired Licensed Copyrights and Licensed Patents of the G.729 Consortium Patent License Agreement, the Licensors of the G.729 Consortium, namely Orange SA, Nippon Telegraph and Telephone Corporation and Université de Sherbrooke (“Licensors”) have agreed to license the same under the existing terms on a royalty-free basis starting January 1, 2017.

For current Licensees of the G.729 Consortium Patent License Agreement, no reports and no payments will be due for Licensed Products Sold or otherwise distributed as of January 1, 2017.

For other companies selling G.729 compliant products and that are not current Licensees of the G.729 Consortium, there is no need to execute a G.729 Consortium Patent License Agreement since Licensors have agreed to license the unexpired Licensed Copyrights and Licensed Patents of the G.729 Consortium Patent License Agreement under the existing terms on a royalty-free basis starting January 1, 2017.

As soon as we hear how this is going to affect Digium Asterisk we will update here.

 

Categories
Blog Design FreePBX Knowledge Base

Voice recognition and Asterisk.

This is primarily about Googles new Cloud Speech API and Asterisk recordings.

Having worked on many Voice rec systems including Mitels attendant system, Oranges Wildfire virtual assistance and Lumenvox’s add on for Digium’s Asterisk system one thing none could do was transcribe speech such as voicemails and this is what people want. There was a startup in the UK called Spinvox  but as anyone knows this wasn’t all it seems and when I questioned them while working on a project they clammed up and withdrew our testing account and the rest is history as they say.

So now we are many years on and Google have their second API for this service. The first API was a little flaky to say the least and came up with some amusing translations. The cloud version is much better and does a good job with most voice and also can be localised.

So what have we done. Well we have mixed together some existing code we use and created a “mini voicemail” that records your message converts it to text saves it as a voicemail and emails the resultant Text and recording to you.  In the process we did find a few “gotchas” with the API for example a pause of more than a couple of seconds will result in the translation stopping there, also a big one is that the translation takes as long as the recording is, and the API has a 60 second limit. Both of these can be overcome by limiting the record time in Asterisk to 60 seconds and using sox to remove silence of more than a second.

exten => s,n,Record(catline/${UNIQUEID}.wav,3,60,kaq)
/usr/bin/sox /var/lib/asterisk/sounds/catline/${origdir}.wav ${PATH}${origmailbox}/INBOX/${FILENAME}.flac  lowpass -2 2500 silence -l 1 0.1 1% -1 0.8 1% 

As you can see from these snippits of code above we have used variables where possible to that it can be incorporated easily with existing asterisk systems using GUIs such as Freepbx, We use the voicemail greetings that the user recorded and also use the email address thats linked with their mailbox for simplicity of management.

Now having Voicemails as text is nice but where it comes into its own is with structured mailboxes or simply put questionnaires where the caller is asked a number of predefined questions and these are recorded as one single voicemail. We already do this for some customers but they still have to have some one transcribe teh voicemail to text to input it. The quality of the Google translation means that soon they will be able to just copy the text over. Other applications are only limited by your imagination, Such as automated voice menus for Takeaways or Taxi firms.

To be Continued…HERE

Categories
Blog Elastix Support

Elastix changes and what it means

This week, significant changes at Elastix were announced, including the involvement of 3CX and the removal of key Elastix versions for download. Since those announcements, many things have been written by many people, and this has left some folks wondering what happened. Sangoma would like to reinforce its commitment to open source, this open letter from Sangoma, will provide our own clarity about how these events affect or involve Sangoma. Sangoma are a professional, global, growing, profitable, engineering-focused, publicly traded company, and this is the only reliable source of information to understand how those recent events affect or involve Sangoma. Other commentary released by other third parties about Sangoma, is not to be relied upon.

Everyone comes to open source software for their own reasons: software developers to do what they love; some to earn a livelihood; manufacturers to augment the project and sell their wares; and most importantly community members to find flexible/cost effective/well-supported solutions to their ‘business problem’ (in our case, for UC/Telecom/PBX needs). In the end, the good projects build something bigger than themselves… a community, a solution, and an opportunity for end users to utilize the project to build their own businesses. Over the course of a project many people will enter and exit those communities as their needs change.

As the primary investor in and developers of FreePBX, Sangoma actively works with many different members of the Open Source Telephony (OST) community, including Asterisk Developers, other FreePBX-based distros (including Elastix!), and many third-party hardware/software developers and manufacturers. As just one example, we have a great relationship with Digium and talk with them on an almost weekly basis, even though many consider us competitors. This may seem surprising to some, as many folks would think we might be bitter enemies. In fact, the opposite is true…we encourage and help those products to compete in the marketplace on their own merits. And this is entirely consistent with the commitment Sangoma has demonstrated to open source for many, many years over the time when we worked hard to also make Asterisk better. When Sangoma took over stewardship of FreePBX, we reiterated this statement clearly and unequivocally.

So Sangoma continues to work very hard every day, and invests many millions of dollars each year, in order to build strong relationships and to benefit to the entire open source telephony community. There is a saying that ‘a rising tide lifts all boats.’ Thus, it is usually counter-productive for open source contributors to battle with each other. In other words, there is no reason for them to fight over the same slice of pie, when there is an entire cake that no one is touching.

Their approach was no different with Elastix. For over a decade, Sangoma has been a direct supporter of Elastix, in many, many different ways, visiting them in Ecuador many times. They supported the project financially, They attended/exhibited/supported/spoke at multiple ElastixWorld events over many years, They cooperated with their distribution partners who also supported Elastix, They invested in R&D to ensure their products (software and hardware) were compatible with Elastix, etc. The list goes on and on.They had (and hope, still have), excellent relationships between the companies, in all parts of the organizations right up to the CEO level of both companies.

With recent changes at Elastix, some people/blogs/websites have made comments which claim that the removal of Elastix downloads of version 4 or MT, was in some way caused by Sangoma/FreePBX, due to concerns about compliance with GPL conditions. That is not true and They wish to set the story straight.  Sangoma hold ourselves to high ethical standards, and as a publicly traded company as well, setting the record straight with facts and not rumours, is both important and required.

While it is indeed true that Sangoma pointed out to Elastix some time ago, that there was a copyright issue,They did so in a very friendly manner, with words carefully chosen to be respectful of the long term relationship between the companies, and critically, to ensure that this important relationship continued. It was a 2015 letter from CEO to CEO, and certainly did not suggest any legal action, since it was not that kind of letter at all…it was a positive, complementary letter seeking to deepen the relationship, not harm it. That letter was sent shortly after Sangoma acquired FreePBX, when they made it a priority to reach out to PaloSanto to reinforce that the Elastix Project was a valuable strategic partner to Sangoma. It was in no way threatening, did not ask for, was not intended to, and given it was 2015, did not cause any versions of Elastix to be withdrawn. Elastix decision this week to shutdown these versions is a business decision not a response to Sangoma. While it seems that these days, the number of open source projects that remain truly open source is definitely on the decline, Sangoma’s commitment to open source remains as true today, as always.

And while it is admittedly a little unusual for companies to do so, in this case, for full transparency to the open source communities that they respect so very much (and to dispel any untrue rumours or claims), the entire letter is available. They share it for those who need confirmation of the above statements, and to reassure the Elastix community that Sangoma continues to be committed to you as well as to the entire Latin America region (and would be honored to have you consider joining the family)

This page is a shorted and edited version of Sangoma’s announcement at https://www.freepbx.org/what-happened-to-elastix/  follow the link for the full version.

Categories
Knowledge Base Sangoma

Building FreePBX CallCenters

Leo D’Alessandro, Product Marketing Manager at Sangoma, and Frederic Dickey, VP of Product Management at Sangoma, will in this webinar explain how to build an efficient contact center cost-effectively with Sangoma’s FreePBX / PBXact UC.

In this webinar, you’ll learn how the many ways FreePBX / PBXact UC can solve your contact center requirements:

• How calls are best routed using call queues
• Maximizing Agent Productivity and Customer Satisfaction with automated Queue Callbacks
• Integration with desktop and CRM
• Monitoring live call metrics
• Reporting tools to analyze overall performance

WEBINAR: Building Your Contact Center with FreePBX / PBXact UC from Sangoma on Vimeo.

Categories
Asterisk Support Knowledge Base Security

Catching the IP of anonymous callers on Asterisk servers

Hi just sharing a simple bit of dialplan to catch anon callers ip addresses when using freepbx and Anonymous callers is set to yes, which is needed for some suppliers.

Normally I would say lock your firewall to only known IPs, but in some cases this isn’t possible

Im sure if you have a Asterisk server with a public IP you will have seen calls on the console screen where the call is to a destination but the callers are exten@yourserver . Well this little bit of dialplan at the end of you default sip context should catch them and log them with the ip of the originating server

In extensions_custom.conf add the dialplan below

[catchall]
exten => s,1,Noop(Dead calls rising)
exten => s,n,Set(uri=${SIPCHANINFO(uri)})
exten => s,n,Verbose(3,Unknown call from ${uri} to ${EXTEN})
exten => s,n,System(echo "[${STRFTIME(${EPOCH},,%b %d %H:%M:%S)}] SECURITY[] Unknown Call from ${CALLERIDNUM} to ${FROM_DID} IPdetails ${uri}" >> /var/log/asterisk/sipsec.log)
exten => s,n,Hangup()

Then in Custom Destinations add a destination as  catchall,s,1

so you now get in your logs

[May 1 00:11:06] SECURITY[] Unknown Call from  to 900441516014742 IPdetails sip:101@37.75.209.113:21896

 I hope this is some help to you, It allows other scripts to pick up this address and add it to your firewall.
Categories
System Status

DNS issues affecting calls and routing

On 21-10-2016 there had been a widespread DDOS attack initially in the USA. This has affected service of some of our key voice and DNS service suppliers.

We monitor many sites and run monitoring ourselves and receive status updates from suppliers.

Below are some of the recent ones and some sites reporting the issue

http://www.diario4v.com/tendencias/2016/10/21/ataque-hacker-afecta-twitter-amazon-spotify-reddit-11816.html (you will need to translate)

http://money.cnn.com/2016/10/21/technology/ddos-attack-popular-sites/

https://www.dynstatus.com/incidents/nlr4yrr162t8

Update
Dyn Managed DNS advanced service monitoring is currently experiencing issues. Customers may notice incorrect probe alerts on their advanced DNS services. Our engineers continue to monitor and investigate the issue.

Customers with questions or concerns are encouraged to reach out to our Technical Support Team.
Posted 4 minutes ago. Oct 21, 2016 - 18:23 UTC
Update
Our engineers continue to investigate and mitigate several attacks aimed against the Dyn Managed DNS infrastructure.
Posted 34 minutes ago. Oct 21, 2016 - 17:53 UTC
Update
This DDoS attack may also be impacting Dyn Managed DNS advanced services with possible delays in monitoring. Our Engineers are continuing to work on mitigating this issue.
Posted about 2 hours ago. Oct 21, 2016 - 16:48 UTC
Investigating
As of 15:52 UTC, we have begun monitoring and mitigating a DDoS attack against our Dyn Managed DNS infrastructure. Our Engineers are continuing to work on mitigating this issue.
Posted about 2 hours ago. Oct 21, 2016 - 16:06 UTC

Gradwell:

Our upstream supplier is investigating a DNS issue, which is believed to be causing the problem.

Magrethea

We are now able to confirm that two nodes on our network where impacted by DNS issues between 17:13 and 17:45 today. As many of you will be aware there have been some major DOS attacks today which impacted a number of key sites at this time so we are attributing this issue to that attack.

We will continue to monitor and apologise for the inconvenience this outage has caused our customers.

As can be seen this is out of our control and is affecting many users worldwide.

Categories
System Status

Hetzner Router fault Core23

Router fault Core23
Type: fault message
Categories: network
Start: September 15, 2016 09:00:00 EDT
End: Unknown
Description: Currently a disturbance on the router Core23 exists. Our engineers are working hard on the analysis of causes and resolve the
problem. Please be patient. Once new information is received, we will inform you on this website. We apologize for the inconvenience. Thank you for your understanding.
Affected: RZ17, RZ19, RZ20, RZ21

update: September 15, 2016 10:00:00 EDT
The problem is currently solved. Core23 is routed empty for further analysis of the underlying problem.
Categories
System Status

Hetzner Router fault RZ19 (ex9k1.rz19 and ex9k2.rz19)

Type: fault message
Categories: network
Start: September 13, 2016 16:40:00 EDT
End: September 15, 2016 08:17:00 EDT
Description: Currently, a fault has occurred on the router and ex9k1.rz19 ex9k2.rz19. Our engineers are working hard on the analysis of causes and resolve the
problem. Please be patient. Once new information is received, we will inform you on this website. We apologize for the inconvenience. Thank you for your understanding.

update: September 13, 2016 17:05:00 EDT
It seems that this problem is caused by a fault line card to an upstream router. The problem could be remedied. We will continue to discuss behavior of the router accurately observing and this incident with the manufacturer.

update: September 15, 2016 08:17:00 EDT
Apparently the problem occurred again. We have the affected hardware now replaced precautionary. We apologize for the inconvenience. Thank you for your understanding.