Archive | July, 2011

RightFax Showcased at Cisco Live!

OpenText RightFax exhibited at Cisco Live 2011 in Las Vegas, NV from 7/10 to 7/14.  As a Preferred Solution Developer member in the Cisco Solution Developer Network (CDN), OpenText RightFax is a recognized leader in providing IP faxing solutions to Cisco clients and partners.  This year’s exhibit hall discussions included our completed RightFax and CUCM 8.x interoperability, as well as our recently certified RightFax 10 Branch Office interoperability with the Cisco UCS Express/SRE-V platform.  The combined Cisco and OpenText RightFax solution supports organizational requirements at the branch office where application survivability and compliancy are requirements. 

Cisco Live was a great success for OpenText and we were able to discuss RightFax with existing clients, interested organizations, and partners alike.  Telecom Reseller took an interest as well.  Listen to the Telecom Resller podcast/interview.

Learn more about RightFax at www.rightfax.com.

Hats Off

At the recent Global Fax Summit, OpenText customers and partners gathered to learn the latest on all things related to enterprise fax management.  At this conference, I was reminded of our global reach and how our partners help solve major business problems with their expertise and a solid set of document management products. The meeting represented something of a celebration for the OpenText Fax and Document Distribution Group as this year marks a major milestone for RightFax since its start 25 years ago. 

Matthew Brine, Vice President of the OpenText Fax and Document Distribution Group states, “The Global Fax Summit allows us to connect with our partners and customers and provides an opportunity for us to express how important they are to our continued success.”

So hats off to our award-winning partners that were recognized for their achievements during the Global Fax Summit. Keep up the good work.

Top Reseller FY11 North America: Advantage Technologies

Largest % Growth FY11 North America: Ingenium Software LLC

Top Reseller FY11 Latin America: Telemikro Ltd

Largest % Growth FY11 Latin America: Redcom, Inc

Top Reseller FY11 Europe : Avanquest UK Limited

Largest % Growth FY11 Europe: Metastore

Top Reseller FY11 MEA: Vox AmVia Pty Ltd

Largest % Growth FY11 MEA: SquareOne Technologies

Top Reseller FY11 Asia/Japan: Macnica Networks Corp.

Largest % Growth FY11 Asia/Japan: Jebsen & Jessen Communications

Top Reseller FY11 Australia/New Zealand: Axient Pty Ltd

Largest % Growth FY11 Australia/New Zealand: Axient Pty Ltd

Essar Replaces Fax Machines with FoIP Using RightFax Integrated with MS Exchange and Avaya

 

By Roopesh Mistry and Ruchir Sharma, Rincon India

It is always a pleasure to meet CxOs of large corporations with a vision to consolidate infrastructure and go green. The Essar Group is a multinational conglomerate and a leading player in the sectors of steel, oil and gas, power, communications and business process outsourcing (BPO), shipping, ports and logistics, projects, and minerals. With operations in more than 25 countries across five continents, the group employs 70,000 people.

When we met Mr. Jayantha Prabhu, CTO, Mr. Prasad Patil – DGM IT and the IT team, they were using multiple fax machines of different brands spread across the group and managing these fax machines was proving to be a challenge. They opted for OpenText RightFax as a centralized solution and decided to integrate RightFax with their existing infrastructure i.e. Microsoft Exchange and Avaya VoIP.

With RightFax integrated with MS Exchange, Essar employees manage their faxes directly from the already familiar mail interface. Sent and received faxes are automatically archived for immediate or later use. By integrating RightFax with their Avaya IP infrastructure, RightFax is now on a virtual server with high availability.

We plan to further fax-enable their MS SharePoint collaboration platform, SAP system and Microsoft Dynamics CRM Servers.

Read the complete case study.

I Need to Send a Fax, How Hard Can It Be?

In my May blog titled “A New Web Service in Town”, I introduced the release of RightFax Web Services—now available through OpenText Professional Services.  In this blog, I’ll tackle the question of how to send a fax in light of the simple and user friendly nature of RightFax Web Services.   

There are many ways to send a fax programmatically…using, for example, COM API, FCL, XML API, Java API and embedded codes.  Each has its own purposes but most are fairly complex and require custom APIs to be installed, print drivers, or the RightFax Production Module to be running.

When using C# (Java is just as easy) and our RightFax Web Services, however, things become much simpler.

Assuming you already have installed RightFax Web Services, the best way to learn this is to work with the NetFormsSample provided with the software.  For the purposes of this blog, I am running the RightFax Web Services on my development environment. 

I begin by adding the Sending Service to my project. 

This is already done in the sample. This is being shown for illustrative purposes only.

The result is that I’ve created a proxy (see below) and all the necessary classes and methods required for sending a fax have been made available to my sample.

The first coding step is to create a “ContractConnection” object with tells RightFax Web Services what RightFax Server to use and the credentials to access the RightFax Server.

Let’s discuss this a little further.

I then need tell it what “FaxServer” to use, what “UserName” and what authentication to use. I’ve left the password blank as I am using a test system with no password.  This sample code above is taken straight out of the sample and the class and objects are fully documented in the documentation we provide, as well.

The second step is to create my fax object and add a sample document that I want to fax.

All I am doing is creating the fields that are required for sending a fax, “ToFaxNumber” and “ToName”.  Then update your coversheet settings (optional). 

Next, I input who is sending the fax in “OwnerId” (Optional).  Lastly we deal with attachments—you can have as many attachments as RightFax allows.  This code is taken straight out of the sample, as well.

Success!  I have successfully created my Fax object.  All that’s left to do is send the fax. 

Sample code is below:

So let’s recap what we did:

·         We added a web service reference

·         We created a connection object

·         We created a fax

·         We sent a fax

…in a small amount of code.

We did not need to install an API on every instance where our custom code runs, or drop a file somewhere with embedded codes, or add a printer.

That is it…that is all we needed to do to send a fax!!

Coming up next: tracking what you sent in “I Just Sent a Fax, How Do I Know If It Was Faxed Successfully?”

 

Why A Plus Isn’t Always a Plus, Especially When The Plus Should Be A Plus

How’s that for a title? This blog came out of a question a student asked me in last weeks RightFax class in our Hoofddorp, NL office. He asked about recognizing a plus sign in the phone number. As usual, I had an answer right away for him and told him we would try it out when we got to dialing rules. And when we got there…well, my answer didn’t work. ACK!!! When something like this happens, I like to investigate and then produce a blog or maybe even a video. And here we are.

But before I get to the problem and solution, let me remind you what Dialing Rules are. Basically they allow the fax server to manipulate the fax number that was entered when the outgoing fax was created. Sometimes you want the fax to go out through a special server on a special channel, depending on the sender’s status in the organization, or the time of day, or the country the fax is being sent to, or the size of the fax, or even how busy the local fax server is. All of that and a whole lot more is possible with Dialing Rules. They are really cool!!!

So what about this question of the plus sign? Well, the documentation talks about using a plus in a Dialing Rule pattern as a kind of universal wildcard. When a plus is in the rule, we ignore all other numbers and just apply the rule. Using a plus for a wildcard makes sense because in the US, plus signs never show up in a phone number. Having grown up in Miami with family in the UK, I know that the only way anyone dials an international number is to dial 011, then the country code. We called my grandmother every week and the number starts with 01144 and then a bunch of other numbers I can’t remember. Everyone knows that and if its true in the US, it HAS to be true everywhere else, right?

It wasn’t until I moved to Europe that I realised that the US was in fact the ONLY country on the ENTIRE PLANET that wouldn’t dial that number as +44 and then the rest of the numbers to call my grandmother. OK, my grandmother was never that popular, but you get the idea. Everyone else uses a plus and then the country code. If you don’t have a plus button on your phone, then its two zeros. Roughly half of one percent of the countries of the world use 011 for international. So being able to put a plus sign in the dialing rule is actually pretty important.

But again, a plus sign on its own in a Dialing Rule pattern is a universal wildcard. It matches everything. So when you put a plus sign at the beginning of the rule, every possible fax number is a match. If i have a pattern that is +44123456789, then all outgoing fax numbers will match, even 987654321123456789987654321 or 8675309.

So what’s the answer? Well I assumed that the answer was to put a 00 at the beginning instead of that + sign. That does work if I am using 00 in my fax, but Rightfax does not translate the + to 00. The solution to this problem was buried in an old Knowledge Center article that talked about RightFax 8.7. In that older version, you needed to add some keys to the registry, but thats not necessary anymore. It turns out that you can simply escape the + with a backslash. So \+, then the country code and the numbers is the right pattern to use for an international number for the other 99.95 percent of the world.

Lets say we have a fax server in my Amsterdam office. Most people will copy a recipients fax number into their phone book using the full international number. But when dialing locally, you usually just dial 0, then the rest of the nine digits of the number. So to call +31 123456789, you would actually dial 0123456789 when in the Netherlands, but the +31 version everywhere else (except the US). To deal with this automatically, create a dialing rule pattern of \+31?????????. Then go to number adjustments, remove the first 3 digits, and add a 0 at the beginning.

When we try to send a fax to +31123456789, we can see that 031123456789 is actually dialed.

Maybe you have a deal worked out with your phone company that all calls from one office get a good rate for international calls, but all the other offices make mostly local calls. When a fax needs to go out to a different country, have it sent over the WAN to the other office and go out onto the PSTN there. You could create a rule that looks for all numbers that start with a plus.

As you can see, a plus sign isnt always a plus sign, especially when the plus should be a plus.

Are you using plus signs in your dialing rules? Did you already know about this? If this is useful, let me know in the comments below. You can also contact me on Twitter where I go by the name technovangelist.