
Rev. 1.00 12-02-13 11/41
The SmartNode analog devices now support DTMF caller ID transmission on FXS ports. DTMF
CID protocol can be fully configured using a profile which can be loaded with one of the
following predefined standards:
- ETSI (ETS 300 659-1 Annex C)
- Denmark (TDK-TS 900 216)
- India (NO.SR/ASF-01/03)
- Brazil (Anatel 220-250-713)
Refer to the New configuration commands section to find out how to configure this feature.
11716 Crash when a „#‟ character is present in SIP contact header
According to RFC 2396 the „#‟ is not allowed in SIP URI. SmartWare did crash if such a
character is present in the URI of the contact header. This scenario is now handled correctly
and the crash does not occur anymore.
11785 Support for p-called-party-id header
This is a new feature added to SmartWare. It is now possible to configure a SIP interface to
extract the called-e164, called-uri and called-name parameters from the “p-called-party-id”
header (optional, see RFC 3455) in the incoming SIP INVITE. For more details on the changes
made to relevant commands, please refer to the „New Configuration Commands‟ section.
11872 Incoming SIP calls refused with 481 after an IP address change over PPP
This problem occurred when the SmartNode gets a new IP address from the PPP server. In this
case the SmartNode would send an UNREGISTER packet with the old IP. This created a
corrupted state where later on received packets still have the old IP address. As a consequence
these packets are refused with a 481 error message. The solution is to drop all outgoing
packets where the IP address is not valid anymore. I.e. the UNREGISTER is not sent anymore
in this scenario.
11882 Cooling fan always running at full speed on SN4670
The issue is observed during boot-up of an SN4670 device such that the cooling fans would run
at very high speed and then would stop for few minutes and would speed-up again causing
undue noise. The issue is now fixed and the fans on SN4660 devices now run more quietly
during boot-up and normal device operation while still fulfilling their cooling task.
11889 No final answer when receiving BYE
SmartWare behaves incorrectly in the following SIP scenario. SmartWare receives an incoming
INVITE request on a SIP interface. The call is forwarded through call-control and reaches the
state of an early dialog at some point by sending a provisional answer “180 alerting” or “183
proceeding”. Now the originator of the INVITE request terminates the call by sending a BYE
request within this early dialog. SmartWare sends back a “200 OK” to the BYE request, but
Comentários a estes Manuais