(I know, I know, but I have to ask) - 6408/6416s on Rls 11? 2

[TheMitelGuy]

Hello,

I hope everyone is having a great holiday season! It's definitely not a traditional Christmas feeling this year with COVID, but I still hope everyone is managing okay.

I know this question has been asked - I did a detailed search on this in the IP Office forum. It appears the last time this question was asked (and someone replied) was IP Office release 10.0/10.1. I was just wondering if anyone has 6408s and/or 6416s running on IPO 11.x? I need to accomplish two things with this upgrade:

1) Continue to support an "all 6400 series configuration", even though there isn't more than 15x sets. It's not a cost thing - the customer just likes the 6400 series over everything else that is available (IP or TDM).

2) They are wanting to use SIP trunking and use the new CO Line/SIP Trunk feature (where you can emulate 1A2 key-system functionality with SIP trunks)...

I'm hoping this works, but I was just wondering if anyone has any working knowledge on this?

Thanks everyone!
Happy New Year!

 

[tac84]

@TheMitelGuy
I've just plugged in a 9608D+ into a digital port on my R11.0.4.2 and it works fine. Obviously it's not supported but it does work.

As for using line appearance on SIP trunks - that I haven't tried as I prefer to avoid line appearance.

I used to really like the 6400 handsets but I always thought the 9500 handsets are a great replacement especially with the convenience of not using paper labels. Each to their own I guess...



Thanks, Tim
Adelaide, Australia

 

[TheMitelGuy]

@tac84:
You said:

As for using line appearance on SIP trunks - that I haven't tried as I prefer to avoid line appearance.

Can I ask why you said that? I typically find that customers (end-users) prefer the simplicity of "Line 1, Line 2, Line 3" etc. and sharing them amongst all of the sets. Just makes it easier for small offices and/or retail. Just curious what you are finding and why you said that?

Thanks so much!

 

[derfloh]

Just use hunt groups instead of line appearances.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[tac84]

@TheMitelGuy - Sure no problems, I just have always found the PBX operation more simplistic on the Avaya IP Office instead of the key system model. As @derfloh commented, hunt groups are a good options and I find then people have more control such as the ability to log in and out of a hunt group. As for the Line 1, Line 2, etc. This is easily be replicated with using Park buttons such as Park 1, or Park XXX. Call comes in via the Hunt Group, someone answers and the call is for someone else you can just Park the call and provided all handsets have the same Park buttons it can easily be retrieved by any other user.

I guess every user and every technician/programmer will have their own preferences though..


Thanks, Tim
Adelaide, Australia

 

[critchey]

When you use line appearances you are actively fighting how the system is designed to work. You can see this illustrated when you get phone calls on 2 buttons, one on the line appearance itself, and one on the call appearance (where the system is designed to route calls). There is literally no reason to use line appearances anymore with an IPO system and your customer will complain about the many issues line appearances cause. Do yourself a favor and get rid of them, especially with SIP lines where they should of never existed, and setup the system as a true PBX.

The truth is just an excuse for lack of imagination.

 

[budbyrd]

We label the Park keys Line 1 etc. and teach them to use them as the hold key for those customers. Seems to make them happy.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'