IPOffice 406v2 ringing issue 2

[tnlcom]

Hi Guys,

Have an IP Office 4.2 with Version 4.2.4 on it and the two 30 alog packs are also on this level.

Having trouble setting the ringing to normal.

I e. the ring type for ringback by all accounts also dictates the ringing cadence for an outside call transfered to another extension. At the moment the extension is set to type 2 and all calls transfered to it ring with a double external call type cadence. It matters not what setting I give the ring type this does not change. Normal external calls ring o.k. as do internal calls. it is just transfered calls.

This has been upgraded from 4.0.14 to solve another problem and this issue was on that version as well. I have deleted and re-installed the users but to no avail. I have checked the locale settings are set to uk for system tab and anywhere else I can find it.

Now lost for ideas!

 

[Escorthosis]

Yes Yes Yes another IPOffice user that doesn't understand the way Avaya tinkered with this on software change over from 3.x to 4.x.

I've been battling with this 'design intended' change ever since 4.0 came out.
Nobody can tell why it was design intended, but al my customers that either upgrade or get a new install complain about it the very first day.
Me and my collegues do have to tell that this is the way Avaya want's it to work and not how we and all customer want it to work.

@Avaya:
A consultation call (an external caller on hold and dial an internal number) should ring internal and should not follow the divert on no answer if the internal calls isn't ticked.
This is the only way to simply implement some sort of fallback to a receptionist without some very gruwesome programming on huntgroups of VMPro startpoints for every user.

 

[TomMills]

@escorthosis.

couldnt agree more.

i see lots of people moaning about this. i havent seen one that says they think it should work this way

 

[Escorthosis]

Thanks for the support but I don't think it will make any difference to Avaya.

See the following post for how long this has been going on:

http://www.tek-tips.com/viewthread.cfm?qid=1430479&page=1

Sometimes I have a feeling that Avaya is monitoring this forum as well. But altering the transfer behaviour is or to expensive or was 'design intendly' altered to get rid of some unvolvable bugs. As there has been no explanation at all why this behaviour has been altered.

 

[TomMills]

i never saw this issue in 3.2 but have found people complaining more and more recently. most of the from indexs we have "upgraded"

 

[intrigrant]

i did a feature request. never got any response from avaya.
they can provide good service but feature requests are a pain in the *ss for them it seems

 

[tlpeter]

I am used to the ringing now
If they did it because of bug problems then at least admit it

I had succesfully responce on a feature request by sending the same email a second time after a while
Maybe they tought, we better responce or he will never leave us alone


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

 

[tnlcom]

Thanks for all your responses guys, when I checked with my "dealer support" if you can call it that they had no idea of the problem and kept telling me it was the way I programmed the country code on first installation of the system which is crap of course!

The problem here is that a customer with a DDI number cannot differentiate (big word can't spell it!) between a caller transfered from another user and his DDI ringing with an external call. This assumes his phone does not ring for incomming calls.

Of course in the states I believe if I am right Americans have one ring type for all calls as they treat all callers both internal and external with a similar greeting!

I suspected this was a "feature enhancement" pity tey did not ask us first if we wanted it!!

I have to admit to getting a little miffed at the number of software changes coming out that quite frankly customers don't want imposed on them.

Once again, thanks for all your support with this question.

 

[as1981]

Just to add another voice. I also think it's a crazy change, consultation calls ringing as internal makes far more sense.

Andrew

 

[TomMills]

as tnlcom quite rightly put, its another change imposed on users/techs. if americans want it this way, build it into their locale. i dont want it this way, and neither do any of our clients. and by the sounds of things most people feel this way.

out of interest, how do you guys in the states feel about this?

 

[Notsetinstone]

So you guys want the internal call or a transfered call to ring differently than a direct call from the outside. I can see the benefit in this but don't think its a big deal. Here in the US, the Magix and the Partner do have a slightly different cadence on transferred calls kind of like a "ring then beep".

Actually, I get more of a request for the internal user who is calling another internal user to get a different ringback when the target is on the phone. With multiple appearences, the caller can't tell if the target is on the phone so if different ringback were sent to the caller he would know instantly that the person was on the phone.

http://www.nu-tel.com

 

[TomMills]

yeah thats basically it, if an external call being transferred rang with the same cadence as an internal call, that would be ideal.

i can see the benefit of your scenario too notsetinstone

 

[TomMills]

eschorthosis.

have you had an email about the 5.0 beta yet?

have a read through. see if you spot anything relevant