Прошивка процессора MP40 АТС Samsung OfficeServ 7400 для работы в составе IP платформы Samsung Communication Manager, версия g4.13 20140627.
New Version Changes
’14.06.27 G4.13
1. [-/ALL/KOREA] CDR format is changed.
<Issue>
CDR format is changed like SCME’s CDR format
<Reason>
Requirement.
<Modified>
CDR format is changed like SCME’s CDR format
2. [-/ALL/ALL] saving digit ‘#’ in station numbers or feature code numbers
<Issue>
If you save digit ‘#’ in station numbers or feature code numbers, digit ‘3’ was saved instead of digit ‘#’
<Reason>
There was wrong conversion of ASCII code ‘#’.
<Modified>
Conversion of ASCII code ‘#’ is fixed.
3. [-/ALL/-] Changed CDR files’ directory path
<Issue>
CDR files were saved in Root directory of SD card or Nand Flash
<Reason>
In case of MP40 and MP20, if files in root directory are over 20 because of CDR files, they cannot boot up.
<Modified>
CDR files are saved in CDR directory.
4. [-/OS7070/ALL] Pickup Group was not changed
<Issue>
Pickup Group was not changed
<Reason>
There was a problem in a way to get pickup group number.
<Modified>
Fixed it
5. [-/ALL/ALL] REGISTER alarm error
<Issue>
When each user’s register is disconnected, ISP NOK alarm takes place.
<Reason>
There was a bug in saving ISP NOK alarm.
<Modified>
When each user’s register is disconnected, ISP NOK alarm doesn’t takes place.
6. [-/ALL /ALL] PRI incoming call’s reject
<Issue>
You cannot reject a call from PRI by using SIP extension
<Reason>
In this case, OfficeServ sent wrong call clear message to PRI
<Modified>
In this case, OfficeServ send ‘user busy (17)’ instead of ‘normal clear (16)’ in call clear message’s cause value.
7. [-/ALL /ALL] PRI incoming call log’s redial
<Issue>
You cannot redial number that is receiving from PRI call with international or national type.
<Reason>
In international or national type’s call case, OfficeServ sent CID number after deleting first 0 or 00 to SCME
<Modified>
In international or national type’s call case, OfficeServ send CID number without change.
8. [-/ALL /ALL] transfer call’s ringback tone
<Issue>
You cannot listen ringback tone after transferring a call from PRI or Loop trunk
<Reason>
There was a t-switch control error
<Modified>
This t-switch control is fixed.
9. [-/ALL /ALL] wrong ringback tone when making a call to multi ring user.
<Issue>
A slt extension make a call to a sip extension set to multi ring with cell phone through PRI trunk. If cell phone is out of battery, A slt extension user listens voice announce from PRI, though the sip extension is ringing.
<Reason>
There was a t-switch control error
<Modified>
This t-switch control is fixed.
10. [-/ALL /ALL] SLT user’s register disconnection.
<Issue>
SLT user’s register connection was intermittently disconnected.
<Reason>
Internal counter related to register was initialized intermittently
<Modified>
This bug is fixed..
11. [-/ALL /ALL] DTMF sending to specific number (892007 in Italy)
<Issue>
When you make a call to a specific number (892007 in Italy), the PRI network send ‘Call Proceeding’ message and ‘Progress’ message and waiting for DTMF. But OfficeServ cannot send DTMF before receiving ‘connect’ message.
<Reason>
OfficeServ cannot send DTMF before receiving ‘connect’ message.
<Modified>
‘ISDN DTMF Send when Progress’ option is added in DM 5.14.5. If you set this option, OfficeServ can send DTMF before receiving ‘connect’ message
12. [-/ALL /ALL] Reject incoming PRI call with some CLIP
<Issue>
If incoming PRI call with CLIP, SCME rejects the call by sending "403 forbidden" message.
<Reason>
Last 2 channel’s Tel number of PRI lines was not included in default PRI trunk group, SCME rejected this 2 PRI Tel number’s call.
<Modified>
Including last 2 channel’s Tel number of PRI lines in default PRI trunk group,
13. [-/ALL /ALL] Analog trunks tone detection disconnect is not working
<Issue>
Analog trunks tone detection disconnect is not working
<Reason>
Changed tone parameter for new engine was not applied.
<Modified>
Changed tone parameter for new engine is applied.
14. [-/ALL /ALL] CPU Overload alarm
<Issue>
Wrong CPU Overload alarm arose.
<Reason>
CPU Overload value was inaccuracy
<Modified>
Disable CPU Overload alarm feature.