I can’t register a DN in tserver 6.1 for definity. The DN 33000 is an ACD Queue with switch specific set to 3 according to the document. In PBX, it is defined as hunt group.
I don’t know the meaning of “Cause: code_std_loc = 1(CCITT_PubNetLocUsr) cause = 28(C_INVLDNUM C_COV_DONT_ANS)”. Is there anyone knows the parsed message meaning? Thanks in advance.
It depends what “Hunt group” has been configured in Avaya.
If it is a ‘pure’ hunt group (as demonstrated below), the DN cannot be monitored; thus, no message event when its states changed.
A hunt group consists of a master directory number and distributes arrival calls to preset extensions directory numbers.
extension members in hunt group do not require ‘log-in’
calls will be diverted to ‘idle’ extensions
in Avaya, a ‘queuing’ option is avaiable if all preset DNs are busy/in-use
If the DN is configured as hunt group described above, it is not CTI-monitorable by Avaya; Genesys T-server does not monitor such hunt group directory number.
Sample HUNT GROUP configuration (Definite 6.3, non-EAS)
display hunt-group 10 Page 1 of 10
HUNT GROUP
Group Number: 10 ACD? n
Group Name: Test IVR Queue? n
Group Extension: 8100 Vector? n
Group Type: ucd-mia Coverage Path:
TN: 1 Night Service Destination:
COR: 1 MM Early Answer? n
Security Code:
ISDN Caller Display:
display hunt-group 10 Page 3 of 10
HUNT GROUP
Group Number: 10 Group Extension: 8100 Group Type: ucd-mia
GROUP MEMBER ASSIGNMENTS
Member Range Allowed: 1 - 200 Administered Members (min/max): 1 /4
Total Administered Members: 4
Ext Name Ext Name
1: 4460 IVR 1/4 14:
2: 4461 IVR 2/4 15:
3: 4462 IVR 3/4 16:
4: 4463 IVR 4/4 17:
5: 18:
I have come across a similar issue, where most of the DN’s ( configured as ACD queues, switch specific type 3 ) have failed registering to Avaya s8720. Error seen is as following.
Also, these DN’s have just failed to register on the back up link to avaya, but they have registered with the primary link.
I can also see some DN’s which successfully registered with both primary and back up as well
Well, the Cause: A_RESUNAVL says the resource is unavailable to use.
Although Tserver has registered it, the resource on switch side should be ready to use.
May b your switch ran out of resources to provide one for you to use… check with avaya pbx guys - if some errors on switch -
my experience prev was seeing port network blockage and the resources on that pn couldn’t b used…
Yea, resource unavailability is pretty much clear from the logs.
We had a environment restart to fix this issue, but the only positive we got was that all the DN’s registered but only a few registered successfully with both primary and secondary link.
Strange thing is, More than 1000 hunt groups have registered correctly to the same switch on both the links, though rest 462 DNs have failed to register on the back up link.
I am just thinking, if that was an port network blockage, it should have happened with all the DNs, isnt it ? please correct me if am wrong.
Do we have any restrictions on avaya, for registrations of DN’s…I mean any particular no of license or limit ?
Yes of course there is a limit according to licensing.
Those codes are switch side, you should look and understand what CTI is trying to say. Maybe after restore the DN on switch side was not ready yet and therefore was not able to provide service.
It is clearly a switch problem
Its just that the avaya team is not understanding this. Its been a struggle since 2 weeks where they have just stuck to their slogan saying " no issues on avaya side "
I guess that is just the TServer internal thread which manages the DN registration; in the log try to look at the first hunt group which TServer fails to register
