speed dial doesn't follow ars entries

[paderb]

hi @all,

I have an OXO R5.1 with to companies and two different trunks on it. I route the calls via ars for each company to its own trunk. everyone uses the same prefix (0) for external calls. everything works just as it should, except for speed dialing.
when user A of company A dials the speed dialing 8000 the call should go through trunk A, same for company B. But the speed dialing ignores the user settings and always used the first trunk entry in the ars. so the user of company B take trunk A and send the wrong number. But only by external calls via speed dialing.
I hope I explained it correct so you understand my problem.

thanks a lot for help

so long

[sera544]

Hi,

U have a two different trunk, why do u want to go via ARS prefix to dial the number, select the particular trunk or trunk group directly from the seize option in the speed dial, wht difference it gonna make...ur problem will be solved..

cheers
Pandian

[paderb]

hi, thanks for the answer.

unfortunately this won't be a solution for me.

every company has its own trunk and its own public number on the trunks.
so, if user A from company A makes a call, the calling number should be the number of company A and not of company B.
If I configure my speed dial as you suggested, all users will send the number of the trunk configured. so if I would take the trunk of company A alls users, also users of company B, will send the number of company A. and this is no multi company service like in the OXE.

thank you anyway.

so long

[enio.eltz]

Hi Paderb

It has to work. I have some customers with a solution like that. You need to send speed dial to a TG with its code to the ARS table. ARS needs to send the number to the right TG. You need to use TRAFFIC SHARING MATRIX to set TG A for sets from company A and TG B for sets from company B.
Send me the database, I take a look.

Regards.

[enio.eltz]

Hi Paderb

I've seen the database you sent me today. Your configurations are right. I don't have any PowerCPU here to restore the database you sent me to test. I don't have any customer with R8 yet. We can have a bug in this R8.0_030.002 you are using. Try to open a SR with A-LU, I have some customers who have the same configuration you need with previous releases and it works fine.

I hope to help you.

[paderb]

hi,

thanks for checking the database. this problem occurs in R5.1, R6.1 and R8.0. I tried several releases.
unfortunately the customer has R5.1/18.004 and as I know there is no alcatel support on this release. but I will try to open an sr for our testsystem.
I will keep this post up to date, if I will get a solution from alcatel.
thank you anyway.

so long

[enio.eltz]

Hi Paderb

OK. I have OXO from previous releases here. I will do some tests today and I will test your problem together. I post here any solution if I find it.

regards.

[tot3nkopf]

This is normal behavior for OXO. Speed dials follow trunk group not ARS (in the old days we used to configure some kind of ARS when license was not purchased). Workaround for you: users in company A have access only to speed dial category 1 and users in company B have access only to speed dial category 2 (OMC-->user-->speed dial-->untick unnecessary). Configure 2 entries for each speed dial, one with access to company's A trunk group and class 1 and one with access to company's B trunk group and class 2.
You can imagine that company's A users will not have access to company's B speed dial numbers (Oand trunk groups) and viceversa.

Kind of odd that an ACSE for OCS does not know these basic things.

Regards.

[enio.eltz]

Hi

Tot3nkopf is right. I did the test minutes ago and I saw the same behaviour. The solution is set two entries for each number. One for each company and set classes of speed dial for extensions as Tot3nkopf said.

Regards.

[paderb]

Hi,

thanks for the answers and tests you did.
sure I know the basics and btw the ACSE certification for OXO is crap, so please don't talk to me like I'm a newbie.

although this solution works, what would you do about the call by name? when you dial the speed dial prefix itself, this works, I allready knew that. but the most customers have a problem memorizing numbers. so they search by name.
now, if I would configure two exact entries for each number, the name would also be the same. when the user then enters the name, for example "smith", there would be two entries with the same name and same number. so, how would you explain the customer wich one he has to use???
another idea would be to change the names, like Asmith and Bsmith, so the users just have to search the names with an A or B before the name, lol.

in my opinion the OXO isn't able to do real multi company, like OXE can.

so long.