Zeck Audio STAC Force180 Guida di Installazione Scaricare il pdf (Pagina 6)

Rev. 1.00 12-02-13 6/41

The SFP (Fiber) interface present on some SmartNodes is supported with this build. It is

represented with the new port ethernet 1 0 mode and supports the following SFP modules:

 Gigabit Ethernet single/multi-mode Fiber and Copper modules

 Fast Ethernet single/multi-mode fiber modules

SFP modules are automatically detected and configured following the INF-8074i specification

for SFP transceiver. If the SFP module does not follow the INF-8074i specification, it must be

manually configured. See details in the New configuration commands section.

12093 SIP calls over TCP failed

Under certain circumstances SmartWare sent INVITE requests over TCP to a wrong IP

address. This happened for example when the DNS SRV record lookup for the request URI

provided different entries for the UDP protocol than for the TCP protocol and when at the same

time the preferred transport protocol was configured to TCP. The first IP address from the UDP

record was taken as destination for the INVITE request, but the request was sent over the TCP

transport protocol. This has been fixed in a way that for the described scenario the first IP

address from the TCP record is taken as destination and the request is sent over TCP to that IP

address.

12097 DSL supervisor log notifies wrong DSL line state

If the DSL supervisor is enabled (with the command [node](port-dsl)[0/0]# supervisor [

always | observe ]) and the modem is not answering for 1 minute, then the supervisor will

notify a DSL link down followed by a DSL link up event instead of notifying that the modem is

busy. This has been fixed in this release build.

12111 Missing user part from SIP contact header

Since the inclusion of the updated SIP support in 2012-09-17 build series the user part in SIP

contact headers has been missing in SIP requests. This has been corrected and the user part is

included again.

Build Series 2012-09-17

11717 Invalid REGISTER request when spoofed contact is set

When a spoofed contact is set, SmartWare sends the first REGISTER request with a wrong

contact address and over a wrong transport protocol. This has been fixed now.

11846 SIP multipart message support

SmartWare is now able to handle multipart SIP messages. Currently only the Content-Type

“multipart/mixed” is supported. Note that SmartWare is only able to receive multipart messages

and will not send multipart SIP messages. If for some reason more than one body part of type

“application/sdp” is received by the SmartNode it will use only the first SDP body and ignore any

subsequent bodies.

1 2 3 4 5 6 7 8 9 10 11 ... 40 41

Nessun commento

Zeck Audio STAC Force180 Guida di Installazione Pagina 6