Hi,
Looking for some feedback on this,
Currently have an issue with the attendant not being divert calls?
The feature activates however when called , the call rings out.
On a similar note i am receiving these errors:
13/05/09 08:42:59 000001M|00/17/0/000|=3:4106=Error of protocol (code 2, op_code 83 command 29) (FBC/PAC/MAC)
13/05/09 08:43:13 000001M|00/28/-/---|=3:3854=VPU: Command buffer full (Inc 4 File 49 Line 182 Stat1 1)
13/05/09 08:43:29 000001M|00/28/-/---|=3:3854=VPU: Command buffer full (Inc 4 File 49 Line 182 Stat1 1)
13/05/09 08:43:31 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are invalid (error 1)
13/05/09 08:43:44 000001M|00/28/-/---|=3:3854=VPU: Command buffer full (Inc 4 File 49 Line 182 Stat1 1)
Any assistance is appreciated,
attendant forwarding
Re: attendant forwarding
I have had a similar issue today on a R7.1-f5.401-7-as-c6s2 twin CPU 4400 system. Customer had the entity incoming status set to Forward1 and had all calls going there after their 4059 PAC crashed earlier. Was able to fix this by rolling the incoming entitystatus into Attendant group status via the incoming state hours but still getting a major alarm on both CPU's in regards to the following:
(1)CPU_a> entitystat 1
Mon May 25 16:42:21 EST 2009
Customer
secret_ident : 0
outgoing_curr_state: SAMEASATTGP
incoming_curr_state: SAMEASATTGP
spv_party_type : 1
spv_party_nr : 0
own_spv_party_type : 2
own_spv_party_nr : 0
group_manager : 0
prioritary : 0
with_deb : 0
trunk group : 0
music : 600
nds : 38630
Voice Mail attribut
vm_box :
password :
language : 1
vmail_id : 255
society_call_number:
centralised_service : 0
sn_queue_trunk_att : 0
sn_multi_spv_att : 0
(1)CPU_a> 25/05/09 16:42:35 000001M|01/19/-/---|=2:4405=IP Parameters given b
y CPU are invalid (error 1)
25/05/09 16:43:08 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:43:42 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:44:15 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:44:49 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
I have checked twin CPU and netadmin setup which looks fine. Any suggestions?
(1)CPU_a> entitystat 1
Mon May 25 16:42:21 EST 2009
Customer
secret_ident : 0
outgoing_curr_state: SAMEASATTGP
incoming_curr_state: SAMEASATTGP
spv_party_type : 1
spv_party_nr : 0
own_spv_party_type : 2
own_spv_party_nr : 0
group_manager : 0
prioritary : 0
with_deb : 0
trunk group : 0
music : 600
nds : 38630
Voice Mail attribut
vm_box :
password :
language : 1
vmail_id : 255
society_call_number:
centralised_service : 0
sn_queue_trunk_att : 0
sn_multi_spv_att : 0
(1)CPU_a> 25/05/09 16:42:35 000001M|01/19/-/---|=2:4405=IP Parameters given b
y CPU are invalid (error 1)
25/05/09 16:43:08 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:43:42 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:44:15 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
25/05/09 16:44:49 000001M|01/19/-/---|=2:4405=IP Parameters given by CPU are inv
alid (error 1)
I have checked twin CPU and netadmin setup which looks fine. Any suggestions?
SWINSTU
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
- frank
- Alcatel Unleashed Certified Guru
- Posts: 3169
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: attendant forwarding
Yeah, either open a ticket with Alcatel-Lucent , or upgrade the attendant console and eventually the PBX release ... I'm sure there is a fix for this.
Code Free Or Die