Прошивка OfficeServ OAS v2.10 20160727
Добавлено: 23 авг 2016, 23:21Прошивка VoIP платы OAS для АТС Samsung OfficeServ7200 и OfficeServ7400, версия 2.10 20160727.
New Version Changes
’16.07.27 V2.10
[New features]
1. [#TE165032/ALL/ALL] OAS card Lockup (Reported by Australia)
<Description>
When OAS received unspecific multicast Packet, Intermittently OAS Card is locked up.
<Cause>
We assume that unspecific multicast Packet made OAS Card lockup
<Resolution>
OAS card drop all of multicast packets for solving this lockup
2. [#TE163029/ALL/ALL] Fax T.38 Issue (Reported by UK)
<Description>
OfficeServ is configured to use Fax Pass Through in MMC835.
When user who is OfficeServ side send fax, OfficeServ send INVITE and receive 200 OK.
After that when OfficeServ receive reINVITE requesting T.38. Sending Fax is failed.
<Cause>
In case OfficeServ is configured to use Fax Pass Through in MMC835 and received reINVITE requesting T.38 from the other side sends, OfficeServ proceeds to use T.38.
OAS card have to change media type from VoIP to FoIP(T.38). But didn’t change media type
<Resolution>
In this case, OAS card changes media type from VoIP to FoIP(T.38)
3. [-/ALL/ALL] THC(TDM Hairpin Connection) Failure (Reported by Australia)
<Description>
THC (TDM Hairpin Connection) NACK happens on OAS card intermittently
For your reference, THC is the feature to copy TDM Time slot data to TDM time slot instead of packetizing TDM Time slot data when outgoing call via SIP trunk comes back to another SIP Trunk as incoming call.
<Cause>
When received INVITE/200 OK/ACK with SDP have own IP address and wrong port in SDP,
there is THC failure.
<Resolution>
In this case, application block don’t send THC command like this error case to DSP block.
New Version Changes
’16.07.27 V2.10
[New features]
1. [#TE165032/ALL/ALL] OAS card Lockup (Reported by Australia)
<Description>
When OAS received unspecific multicast Packet, Intermittently OAS Card is locked up.
<Cause>
We assume that unspecific multicast Packet made OAS Card lockup
<Resolution>
OAS card drop all of multicast packets for solving this lockup
2. [#TE163029/ALL/ALL] Fax T.38 Issue (Reported by UK)
<Description>
OfficeServ is configured to use Fax Pass Through in MMC835.
When user who is OfficeServ side send fax, OfficeServ send INVITE and receive 200 OK.
After that when OfficeServ receive reINVITE requesting T.38. Sending Fax is failed.
<Cause>
In case OfficeServ is configured to use Fax Pass Through in MMC835 and received reINVITE requesting T.38 from the other side sends, OfficeServ proceeds to use T.38.
OAS card have to change media type from VoIP to FoIP(T.38). But didn’t change media type
<Resolution>
In this case, OAS card changes media type from VoIP to FoIP(T.38)
3. [-/ALL/ALL] THC(TDM Hairpin Connection) Failure (Reported by Australia)
<Description>
THC (TDM Hairpin Connection) NACK happens on OAS card intermittently
For your reference, THC is the feature to copy TDM Time slot data to TDM time slot instead of packetizing TDM Time slot data when outgoing call via SIP trunk comes back to another SIP Trunk as incoming call.
<Cause>
When received INVITE/200 OK/ACK with SDP have own IP address and wrong port in SDP,
there is THC failure.
<Resolution>
In this case, application block don’t send THC command like this error case to DSP block.