SIP Fallback working on 4.1(9) - Not in TB90 3

[MrIPO]

FYI

The 4.1 Product Description now states that SIP fallback is supported when using ARS

http://marketingtools.avaya.com/kno...ost_routes.htm?zoom_highlightsub=sip+fallback

We have just tested here on 4.1(9) and SIP fell back to PSTN/ISDN under the following, this was using SIP Shortcodes in Main Route 50 and Falling back to a Second ARS route from Route 50 on a ?,.,0,Dial Shortcode to ISDN after 5 second timer setting.

1, SIP line set to 1 channel
Made one call out SIP trunk, and then a second call it waited 5 seconds and fell back to ISDN Ok for the second call

2, SIP Fallback when LAN 1 port disconnected
Waited 5 seconds and fell back to PSTN

3, SIP Fall back when upstream firewall disconnected LAN 1 was connected
Waited 5 seconds and fell back to PSTN

It would seem on 4.1 the SIP signaling is more advanced on the IPO so if it receives no response back from The ITSP it does in fact fall back using ARS settings. This was not the case in 4.0 and caused us real pain.

http://www.iporesource.com

 

[intrigrant]

Thats why Tier3 advise to upgrade to 4.1 if there is a problem on another version.
I upgraded a 4.0.104007 site yesterday, the customer had a big list of annoying problems.
After the upgrade there was only one problem left and i did not change anything in the config!


NIHIL NOVI SUB SOLE

 

[puregold]

Thats good.

Star.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[aarenot]

MrIPO this is very helpful.

 

[aarenot]

Intigrant,
you should not have had to upgrade the entire system to get the previous releases features to work. That is not really supporting the previous release IMHO.

 

[tlpeter]

Aarenot , i think it is upgrade because 4.0.10 is a bad version and with upgrading he solved a lot of problems without doing anything else
And not to kick down 4.0 the 4.0.14 is a good release


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[aarenot]

tlpeter,
My point was that support telling you to upgrade from 4.0 to 4.1 in order to get 4.0 features working properly is not really supporting 4.0 but diverting to 4.1

I could go on, but let me suffice by saying this. Features which are not tested, and verified close enough to actually working properly when a new release comes out, that they cannor be ironed out to work in the following maint releases, requiring the next full release before they actually work should have been left off in the first place so we do not sell them a year or so before they are ready.

Again, that is just my opinion, and I may be all alone on this one.

 

[Escorthosis]

If I understood correctly when attending the Avaya 4.1 seminar the 4.0.14 will be the last 4.0 release (it was called 4.0.12 on the sheets then). Other bugfixes will be developed on 4.1.xx.
And why shouldn't they all hardware running 4.0 can run 4.1.

 

[aarenot]

Escorthosis,
I agree with moving on to 4.1, and developing it with a new feature set. I do hope that 4.1's stated features will not exceed what it delivers by the time it is in its last maint release.

If you bought a 2007 car that claimed to have 4 wheel drive, and 40 MPG, you would not expect to have to get the next model year to get through a snow drift using 4 WD, nor to get above 30 MPG.

They should keep at maint releases at least until they deliver what they promised in the general release which is usually 3, or 4 maint releases back. They should be good enough, and not overpromising enough to do that.

Having to upgrade IPO, VMPRO, VMPRO CLIENT, CCC, DELTA, IP SOFT PHONES IN THREE STATES, 100 PHONE MANAGERS, 5 SOFT CONSOLES, RE-INTEGRATE A THRID PARTY ZEACOM, etc., etc. just to get a feature promised one year, and three maint releases ago is a little less than genuine in my opinion. Do not forget that the other systems in the SCN will need to be upgraded as well for no other reason than overpromising features by way farther than should even happen.

I can not believe I am arguing that features should not be expected until the last maint release of a major software release.

 

[tlpeter]

Aarenot i understand what you are saying
I think that they did this on purpose

3.2 should not even excist but the time between 3.1 and 4.0 was too big,so 3.2 came
But with a new software release the stress came and i think that is why it all goes like it goes
There should have been a 3.0DT maitanance release but that did not came
Why ? There is no time to spend on it
All the time they have is put in 4.1 and 4.0
Also the next release is in development and takes a lot of time of the programmers
So i also understand completely that 4.0 will not be further released
And yes you are right ,it can be very frustrating



ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[aarenot]

tlpeter,
I agree too many new feature releases have been pushed out.

 

[tlpeter]

But that is also a bit the very fast way of living.
There must be a quick responed for new features and releases or you can forget is a big company


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[aarenot]

tlpeter,
Quick is the only priority if the product name starts with Mc.

I also like to take a quick Chit since it gets you out of the stink faster.