IPO to Avaya Communication Manager FoIP

[CarGoSki]

So for the last two months I have been working with a global team trying to figure out why we just can not seem to get the connection between an IPO and an s8700 to complete FoIP calls.

We were able to set this up in our lab using IPO and our house s8700 and everything worked fine.

We were finally able to meet Avayas guidelines for QOS when packet shaping was implemented between the customers two sites. Unfortunately this did not resolve the issue.

Today, Avaya tells me that the Engineers toolkit and sales documentation is wrong in stating that FoIP works between IPO and ACM. That is outrageous in my opinion.

They are apparently backing away from supporting this issue by claiming the documentation is wrong. The problem of course is that the capability was introduced in 2.1 and continued to be claimed to exist in all of the 3.0 documentation. Also I still believe that this will work.

Have any of you heard of a retraction on FoIP capabilities between IPO and ACM since 2.1?

 

[MrIPO]

The IPO FoIP (Fax Over IP) is IPO propriety, and so I think you will have issues, strange that you are unable to get it working with ACM, but not surprising, with newer software another untested feature I would guess. You would think this is something AVAYA would have wanted to do for the US Market and make sure it worked with V3.0. I myself have never tried.

It would be much easer if they just used T.38. The ITU standard for Fax Over IP

Umm anotherprivatebuild !!!

 

[VOiDDude]

I wouldn't use it myself because but there exists since 2.1 something like a "hidden parameter" to enable expermimental faxing between the IPO and CM. I can't remeber what it was but give a call to Avaya.

 

[crashtest1000]

It has taken a couple months to get voice working between our ACM and IPO so Fax well good luck.

The docs are all out of date for thihs application. So you just have to guess

 

[VanZenden]

When I was working on FoIP (IPO ver. 2.0), Avaya gave me this parameter:

Users / NoUser / SourceNumbers - and add an entry DEFINITY_FOIP

The entry IS case sensitive, the change is not mergeable, you must reboot the IPO...

hope it helps...

 

[CarGoSki]

VanDenden said: When I was working on FoIP (IPO ver. 2.0), Avaya gave me this parameter:

Users / NoUser / SourceNumbers - and add an entry DEFINITY_FOIP

The entry IS case sensitive, the change is not mergeable, you must reboot the IPO...

hope it helps...
-------------------------------------------------

Really.... So put the entry into the nouser profile. I'll try it.

 

[CarGoSki]

BTW VanDenden.. Were you able to get it to work?

 

[VanZenden]

I can't remember if this parameter worked with me

FoIP only worked when Avaya gave me private build v2.0 for IPO 403. future GA releases (2.x & 3.0) didn't work.

On one occasion FoIP worked with v2.1.24, but after a succesful fax transfer, SOE reseted itself, but at least it worked

 

[Morrack]

CarGoSki, please let us know if it works. I'm quite curious about this one



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[VanZenden]

CarGoSki,

In case parameter I gave won't work, then try to disable/turn off ECM (Error Correction Mode) on a fax machine (ECM can be usually found in Advanced menu).

 

[CarGoSki]

The funny thing is that after finally being allowed to access the ACM ourselves we found that the ACM was sorely lagging in its firmware upgrades.

Liar, liar pants on fire. The european Business partner led us all to believe what was not true. Soooo we will upgrade the firmeware ourselves tomorrow.

Gotta love the connected world!

 

[CarGoSki]

Well we are able to complete foip calls from IPO to ACM. Just not all the time. It appears that the IPO network services would stall occasionally when foip calls are in progress.

Today Avaya tells us that they intend to scale back on new features and focus on making IPO stable. It would appear that there is a cost for this and the first casuality is FoIP from IPO to ACM.

As of today Avaya no longer supports FoIP from IPO to ACM.