DID on SV8300 Problem

[cnyamukondiwa]

Good Day All,

May you please assist me on the DID Problem that I have on the SV8300.
The problem I have is that when when you call the DID extension, it rings only once at the extension and then goes to the operator extension.

Thanking you in advance.

Regards,
Cleophas

 

[cnyamukondiwa]

Good Day Colleagues,

I have managed to list command 08 from the two systems and attached are the files.
Thanking you in advace.
Rgds,
Cleophas

 

[PFD45]

I wonder if the issue might be related to disconnect supervision?

If I understand your test, a DID call is successfully made to an extension then the extension hangs up. Then a second DID call to the same extension rings once and then the call goes to the operator.

So how long do you have to wait before a DID call to the same extension goes through? It seems like the question is why does the 2000 thinks the extension is unavailable for that period.

Maybe if you run the E8 command on the test extension immediately after the first test call we might see what state the 2000 thinks the extension is in???

 

[cnyamukondiwa]

Dear PFD45,
I would like to thank you for your response.
As I have found out during further testing,if you reset the PRTA card, or the system, and you do a DID test call, that call goes through without any problems.
The second time you try a DID test call to that extension or any other extension, the call rings once and then goes to the operator extension.
Can the Telco, play a part in this type of behavior?

I do not have Command E8 in my PCPro that I am using, could this be a different version of PCPro as I am using Version 9.0.0.303

Thanking you in advance.
Rgds,
Cleophas

 

[PFD45]

So you have to re-set the PRTA card (or system) just to get 1 successful call to an extension. After that, ALL calls to that extension ring once and then goes to the operator . . . unless you re-set the PRTA card.

Ok, that does not sound like telco or disconnect supervision.

I'll ponder it some more.

 

[OzzieGeorge]

I have had problems like this (quirky) when the ISDN protocol was set to Australian ISDN when the lines are ETSI, it works but strange things happen. Check the protocol being supplied by the service provider and the setting on your PABX.

 

[belevedere]

If you change the protocol remember to reset the card afterward.

 

[OzzieGeorge]

Ok so Cmd 08 points of difference are.....

140 0 Message Waiting indication on Line Key of Multiline Terminal

267 0 Hotel feature (Wake-up, Do Not Disturb, Message Waiting, Room Cutoff) records printout on Hotel printer, and the report is sent to PMS when setting or resetting the hotel feature from Hotel Console or Administrative station

294 0 MW lamp indication on Multiline Terminal to which Message Waiting/Message Reminder is set

400 1 Send Calling Party Subaddress to ISDN network

443 1 Type of Voice Mail System (VMS)
708 1 Number of digits for station number in MCI message format sent to VMS from CPU RS-232C port

839 0 Sending of OAI SMFN with intermediate information via OAI queue

909 1 Allow built-in modem/speech synthesis service

1861 0 Not in Manual

1875 0 Not in Manual

These are the settings for the system that isn't working. The two that are of immediate concern are the two that aren't in the manual and are not set to the default of 1. most of the others can be set the way they are for a good reason but 400 may be worth checking. Try a system reset after each change (make sure you save it first).

 

[OzzieGeorge]

Do you have a backup of the system and why have you not tried swapping the IP daughter board to the new CPU if that is the only way you have had to connect?

 

[OzzieGeorge]

D@mn Did it again, mixed up the two threads! pleased ignore my last post!

 

[cnyamukondiwa]

Dear Colleagues,

I managed to resolve the issue of the DID problem.
I changed prog:410<01<01 to 410<01<07 and the DID is now working.
Thank you all for the support.

Rgds,

Cleophas

 

[OzzieGeorge]

Sounds like you have group diversion set up. Check command 162 to see if the extensions are set to a group. It could also be that it was automatically switching to night mode and command 30xx isn't set for DID in night mode. Either way, it would be worth checking so that you understand what is happening as it could happen again if a call rings long enough without being answered.