Zeck Audio STAC Force180 Guia de Instalação Página 12

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 41
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 11
Rev. 1.00 12-02-13 12/41
does not send any final answer to the INVITE request. This is now corrected and SmartWare
sends in addition to the “200 OK” to the BYE also a “487 Request Terminated” answer in
response to the original INVITE request.
11891 SN4660/SN4670 Rev C and Rev D support
The new SmartWare build has now integrated support for the latest revisions of the
SN4660/SN4670 products.
11895 Ethernet switch problem on SN4660/SN4670
Two problems related to the Ethernet switch chip on SmartNodes 4660/4670 were fixed. The
bootloader was crashing when two network cables where connected. When Ethernet 0 and 1
where both connected to the same switch the IP routing would fail because the software did not
maintain separate MAC address tables for each port.
11898 Enhancement of software upgrade procedure
The software upgrade procedure in SmartWare is enhanced to support software deliveries
packed as tar files and the ability to upgrade in the future to a different Operating System.
11899 SIP Hold/Unhold behavior
When the SmartNode is set on hold with the SDP a=inactive during a SIP call, the SmartNodes
responding SDP would always be a=recvonly. The behavior was adjusted so that SmartNode
responds to a=inactive with a=inactive and to a=sendonly with a=recvonly. This behavior
change is needed to be compliant with Microsoft LYNC servers among others.
11902 SIP q-value of 1.0
The Q-value feature did not allow sending a maximal value of 1.0. Now it is possible to send all
values between 0.0 and 1.0.
11929 SN-DTA clock synchronization
On the SN-DTA device a problem related to ISDN clock synchronization has been fixed. It
occurred if an external TE device was configured to get its reference clock from the SN-DTA‟s
NT port. Especially if the connected device was a PBX which itself served FAX machines, the
problem resulted in failing FAX transmissions.
11932 SIP 503 error handling
SmartWare was not correctly hunting for SIP peers if a DNS lookup returned multiple A records.
In case the SmartWare SIP gateway receives a list of possible IP addresses it should try to
connect to the first IP address in that list. If this does not work due to a network problem or if the
peer SIP side sends a 503 Service Unavailable, the SmartWare should try the next IP in the list.
Now in one very specific case SmartWare received a 100 Trying between the initial INVITE and
the 503 and was therefore not further trying to connect to the next IP address. This behavior
has been changed to allow proper SIP destination hunting.
Vista de página 11
1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 40 41

Comentários a estes Manuais

Sem comentários