Release Notes. DRG SW R2N33 Release Notes

Transcription

1 Release Notes DRG SW R2N33 Release Notes

2 DRG SW R2N33 Release Notes DOC-DRG_R2N33-RN. Published June 6, Copyright and Legal Notice Copyright 2012 Genexis B.V. All rights reserved. DRG, DRGOS, DRG bootloader, program models and other software, software content, and this documentation ( the Intellectual Property Rights ) are protected by the Dutch Copyright Act (Auteurswet) and, if applicable, the Dutch Patents Act. All and any copying and distribution of the Intellectual Property Rights, without authorization by Genexis is prohibited. The prohibition includes every form of reproduction and distribution. Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change without notice. Genexis assumes no liability for damages incurred directly or indirectly from errors, omissions or discrepancies between the software and this document. DRG and DRGOS are tradenames of Genexis. All other trademarks, service marks and trade names are proprietary to their respective owner. Purchasers, licensees and users accept and acknowledge that the products contain components (including components carrying certain firmware) and combinations of components that constitute trade secrets protected by Genexis or its partners. Purchasers, licensees and users warrant that the delivered products will not be opened or dismantled, copied, altered or in any other way modified. Furthermore, purchasers, licensees and users agree not to attempt to reverse engineer, disassemble, modify, translate, create derivate works, rent, lease, loan, or without written permission distribute or sublicense the software, in whole or in part. The products and its hardware, firmware and software, including technical data, may be subject to EU and U.S export control laws, including the U.S Export Administration Act and its associated regulations and the International Traffic in Arms Regulations administrated by the US Department of State, and may be subject to export or import regulations in other countries. Purchasers and licensees agree to comply strictly with all such regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import hardware, firmware and software. Purchasers and licensees are not entitled to, and Genexis is not in any event liable to pay, compensation for damages which delivered products or software has caused to other property or to persons or any other consequential damages, including but not limited to loss of profit, loss of production or any other indirect damages.

3 Contents DRG SW R2N31-R2N33 Release Note Introduction Supported Platform Released Images New Features in DRG SW R2N31-R2N Resolved issues in DRG SW R2N31-R2N Known issues in DRG SW R2N DRG SW R2N29-R2N30 Release Note Introduction Supported Platform Released Images New Features in DRG SW R2N29-R2N Resolved issues in DRG SW R2N29-R2N Known issues in DRG SW R2N DRG SW R2N03-R2N28 Release Note Introduction Supported Platform Released Images New Features in DRG SW R2N03-R2N Resolved issues in DRG SW R2N03-R2N Known issues in DRG SW R2N

4 DRG SW R2N33 Release Notes 4

5 DRG SW R2N31-33 Release Note Introduction This release note describes the software changes from DRG SW R2N31 to DRG SW R2N33. Supported Platform If not otherwise defined, the new features, resolved issues, and known issues apply to all the products specified in Released Images on page 5. Some issues may be dedicated to a specific image or protocol as indicated in the descriptions. Released Images Table 1 shows the supported hardware platforms and corresponding software images in DRG SW R2N33. Table 1 Released Images Hardware platform Image revision VoIP Protocol DRG 11/22 DMA0021 SIP DRG 11/22 DMA0022 H.323 DRG 11/22 DMA0041 MGCP DRG 560/580 DMA0081 SIP DRG 560/580 DMA0082 H.323 DRG 560/580 DMA0083 MGCP DRG 540 DMA0101 SIP DRG 540 DMA0102 H.323 DRG 540 DMA0103 MGCP DRG 100 DMA0202 SIP DRG 100 DMA0203 H.323 DRG 100 DMA0204 MGCP DRG 600-Access DMA DRG 600-Telephony DMA0121 SIP 5

6 DRG SW R2N31-33 Release Notes New Features in DRG SW R2N31-33 No new features are introduced from DRG SW R2N31 to DRG SW R2N33. Resolved issues in DRG SW R2N31-33 The following issues are resolved from DRG SW R2N31 to DRG SW R2N33. Table 2 Bug number Resolved issues Description The parameter XML file defines the telephony service twice The DRG parameter XML file that is used by HDD includes duplicate telephony service definitions SDP Syntax Error The DRG is unable to process SIP messages that contain "-" in Session Description Protocol (SDP) session attributes, such as "a=x-nat:0" DRG does not respond to ARP queries in which "Sender MAC address" is different from source MAC address If the "Sender MAC address" in an ARP query is different from the source MAC address, the DRG does not respond to this ARP query. 6

7 DRG SW R2N31-33 Release Note Known issues in DRG SW R2N33 The following issues are known in DRG SW R2N33. Table 3 Known issues Bug number Discovered Description R2N Parameter values insufficient for COUNTRY param for CLIP Parameter values are insufficient for COUNTRY parameter for CLIP. The parameter value ETSI_DURING_RINGING should be removed, and the following values should be added: 1. ETSI_DURING_DT-AS 2. ETSI_DURING_RP-AS 3. ETSI_DURING_LR+DT-AS R2N TV freezes when multiple STBs are watching the same channel When using multiple STBs connected to DRG560/580, the TV picture may freeze R2N DHCP Option 225 cannot configure SIP server port When using DHCP option 225 for configuring SIP server details, non-default settings for ports are used as the local port, not the SIP server port. Workaround: Always use default ports R2N Echo Cancellation causes loss of voice Under some conditions, when both sides talk, the DRG may stop sending voice traffic for up to 30 seconds. Workaround: Disabling echo cancellation has been shown to stop this issue from occurring R2N H.323: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N H.248: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N DMA0083: DRG stops responding Following configuration changed by HDD, a DRG may become unresponsive and disappear from the network. It must be rebooted to become active again. 7

8 DRG SW R2N31-33 Release Notes Table 3 Known issues Bug number Discovered Description R2N Multicast streams do not stop If a multicast client leaves a group without sending a leave message, the multicast stream will not time out and be removed R2N Turning off IGMP Snooping stops all multicast If IGMP snooping is disabled for one port, all multicast traffic flows are stopped and cannot be restarted R2N DMA0027: SIP registration problem after WAN outage If the path between DRG and SIP proxy is interrupted long enough for the registration to expire, then the DRG may fail to register with the proxy when the disruption is removed R2N DMA0027 R2N14 only sends End Event at Flash Hook Flash Hook, enabled either tapping the receiver or using the R button, only produces an RTP Flash End event. Because no Start event packets are sent, the certain External Class 5 service will not work in customer switches R2N SIP stops working after a final REGISTER response matching transaction but not matching dialog If the DRG receives a response to a REGISTER message where the URI does not match the request, the SIP application may stop working R2N H.323: DRG incoming calls failure Incoming H323 calls may fail on DRG R2N Not able to configure ports on DRG600-Access through HDD For the DRG600, it is not possible to configure ports using HDD R2N SNMP get/set not matching configurations On DRG600A, some SNMP objects may not match the actual device configuration R2N Contact-URI is used for CLIP instead of display name The Contact-URI may be used for CLIP information instead of From-URI. Under normal conditions, these values are the same and this has no effect. 8

9 DRG SW R2N31-33 Release Note Table 3 Known issues Bug number Discovered Description R2N CLIP presentation of number does not work when dial plan contains reverse substitution which includes "+" If the dial plan contains a reverse substitution rule that includes "+", the caller ID value used will not contain the reverse substitution, but will use the value from SIP "from uri" context R2N GUI stops responding after a while after being upgraded to R2N18 The web server is not accessible. But other network applications such as ping and SNMP are not affected R2N No respond to MGCP request when "Max. delay before RSIP" set to 0 If the value of maximum delay before RSIP is set to zero, the DRG will register with the MGCP agent, but will then stop communicating with the agent. Workaround: Use a non-zero value for max delay before RSIP R2N DRG Web GUI does not support Google Chrome The DRG does not fully support Google Chrome. If the user makes some configuration changes on the GUI using Chrome and restarts the DRG, the configurations are not updated R2N TCP RST on incoming call Sometimes during H.323 call setup, DRG refuses the peer TCP connection, which causes the incoming call failure R2N Busy subscriber handles incoming call incorrectly when internal class5 disabled If a VoIP line is configured in External Class 5 service mode and the line is active in a call, when another call comes in, DRGOS does not provide the 486 Busy message, but replies with a 180 Ringing SIP message. This is because DRGOS has Call Waiting Caller ID (CWCID) enabled and thus sends the CW tone and CID information to the handset R2N sipapp crashes during attended transfer between line 1 and line 2 When a voice call is established between two lines (A and B) on the same DRG, if the callee presses "Flash 4" to transfer the call to C, the SIP application in DRGOS may crash. 9

10 DRG SW R2N31-33 Release Notes 10

11 DRG SW R2N29-30 Release Note Introduction This release note describes the software changes in DRG SW R2N29 and DRG SW R2N30. Supported Platform If not otherwise defined, the new features, resolved issues, and known issues apply to all the products specified in Released Images on page 11. Some issues may be dedicated to a specific image or protocol as indicated in the descriptions. Released Images Table 1 shows the supported hardware platforms and corresponding software images in DRG SW R2N30. Table 1 Released Images Hardware platform Image revision VoIP Protocol DRG 11/22 DMA0021 SIP DRG 100 DMA0202 SIP DRG 340/540 DMA0101 SIP DRG 560/580 DMA0081 SIP DRG 600T DMA0121 SIP 11

12 DRG SW R2N29-30 Release Notes New Features in DRG SW R2N29-30 No new features are introduced in DRG SW R2N29 and DRG SW R2N30. Resolved issues in DRG SW R2N29-30 The following issues are resolved in DRG SW R2N29 and DRG SW R2N30. Table 2 Bug number Resolved issues Description Using SNMP to reconfigure access VLANs breaks connection Using SNMP to configure VLANs may cause VLAN configuration to be corrupted H.323 call fails during media capability negotiation When the DRG makes calls over H.323, in rare cases some calls might fail due to incompatibility between the DRG and the terminal device on the other end of the call. If the H.245 terminalcapabilityset message received by the DRG contains some unrecognized capabilities in one entry, the DRG cannot negotiate a correct voice codec with the called party and thus fails to send Open Logical Channel (OLC) messages. If the called party happens to be the slave, the called party cannot send Open Logical Channel (OLC) messages either. Both parties hang in OLC waiting status. When timeout occurs, the call fails DRG crashes behind NAT when server side keep-alive is enabled The DRG crashes after receiving approximately 500 OPTION messages with extensions in the "Via" field. 12

13 DRG SW R2N29-30 Release Note Known issues in DRG SW R2N30 The following issues are known in DRG SW R2N30. Table 3 Known issues Bug number Discovered Description R2N Parameter values insufficient for COUNTRY param for CLIP Parameter values are insufficient for COUNTRY parameter for CLIP. The parameter value ETSI_DURING_RINGING should be removed, and the following values should be added: 1. ETSI_DURING_DT-AS 2. ETSI_DURING_RP-AS 3. ETSI_DURING_LR+DT-AS R2N TV freezes when multiple STBs are watching the same channel When using multiple STBs connected to DRG560/580, the TV picture may freeze R2N DHCP Option 225 cannot configure SIP server port When using DHCP option 225 for configuring SIP server details, non-default settings for ports are used as the local port, not the SIP server port. Workaround: Always use default ports R2N Echo Cancellation causes loss of voice Under some conditions, when both sides talk, the DRG may stop sending voice traffic for up to 30 seconds. Workaround: Disabling echo cancellation has been shown to stop this issue from occurring R2N H.323: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N H.248: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N DMA0083: DRG stops responding Following configuration changed by HDD, a DRG may become unresponsive and disappear from the network. It must be rebooted to become active again. 13

14 DRG SW R2N29-30 Release Notes Table 3 Known issues Bug number Discovered Description R2N Multicast streams do not stop If a multicast client leaves a group without sending a leave message, the multicast stream will not time out and be removed R2N Turning off IGMP Snooping stops all multicast If IGMP snooping is disabled for one port, all multicast traffic flows are stopped and cannot be restarted R2N DMA0027: SIP registration problem after WAN outage If the path between DRG and SIP proxy is interrupted long enough for the registration to expire, then the DRG may fail to register with the proxy when the disruption is removed R2N DMA0027 R2N14 only sends End Event at Flash Hook Flash Hook, enabled either tapping the receiver or using the R button, only produces an RTP Flash End event. Because no Start event packets are sent, the certain External Class 5 service will not work in customer switches R2N SIP stops working after a final REGISTER response matching transaction but not matching dialog If the DRG receives a response to a REGISTER message where the URI does not match the request, the SIP application may stop working R2N H.323: DRG incoming calls failure Incoming H323 calls may fail on DRG R2N Not able to configure ports on DRG600-Access through HDD For the DRG600, it is not possible to configure ports using HDD R2N SNMP get/set not matching configurations On DRG600A, some SNMP objects may not match the actual device configuration R2N Contact-URI is used for CLIP instead of display name The Contact-URI may be used for CLIP information instead of From-URI. Under normal conditions, these values are the same and this has no effect. 14

15 DRG SW R2N29-30 Release Note Table 3 Known issues Bug number Discovered Description R2N CLIP presentation of number does not work when dial plan contains reverse substitution which includes "+" If the dial plan contains a reverse substitution rule that includes "+", the caller ID value used will not contain the reverse substitution, but will use the value from SIP "from uri" context R2N GUI stops responding after a while after being upgraded to R2N18 The web server is not accessible. But other network applications such as ping and SNMP are not affected R2N No respond to MGCP request when "Max. delay before RSIP" set to 0 If the value of maximum delay before RSIP is set to zero, the DRG will register with the MGCP agent, but will then stop communicating with the agent. Workaround: Use a non-zero value for max delay before RSIP R2N DRG Web GUI does not support Google Chrome The DRG does not fully support Google Chrome. If the user makes some configuration changes on the GUI using Chrome and restarts the DRG, the configurations are not updated R2N TCP RST on incoming call Sometimes during H.323 call setup, DRG refuses the peer TCP connection, which causes the incoming call failure R2N The parameter XML file defines the telephony service twice The DRG parameter XML file that is used by HDD includes duplicate telephony service definitions R2N Busy subscriber handles incoming call incorrectly when internal class5 disabled If a VoIP line is configured in External Class 5 service mode and the line is active in a call, when another call comes in, DRGOS does not provide the 486 Busy message, but replies with a 180 Ringing SIP message. This is because DRGOS has Call Waiting Caller ID (CWCID) enabled and thus sends the CW tone and CID information to the handset R2N sipapp crashes during attended transfer between line 1 and line 2 When a voice call is established between two lines (A and B) on the same DRG, if the callee presses "Flash 4" to transfer the call to C, the SIP application in DRGOS may crash. 15

16 DRG SW R2N29-30 Release Notes Table 3 Known issues Bug number Discovered Description R2N 400 SDP Syntax Error The DRG is unable to process SIP messages that contain "-" in Session Description Protocol (SDP) session attributes, such as "a=x-nat:0" R2N DRG does not respond to ARP queries in which "Sender MAC address" is different from source MAC address If the "Sender MAC address" in an ARP query is different from the source MAC address, the DRG does not respond to this ARP query. 16

17 DRG SW R2N03-28 Release Note Introduction This release note describes the software changes from DRG SW R2N03 to DRG SW R2N28. Supported Platform If not otherwise defined, the new features, resolved issues, and known issues apply to all the products specified in Released Images on page 17. Some issues may be dedicated to a specific image or protocol as indicated in the descriptions. Released Images Table 1 shows the supported hardware platforms and corresponding software images in DRG SW R2N28. Table 1 Released Images Hardware platform Image revision VoIP Protocol DRG 34x/54x DMA0101 SIP DRG 600A/Ease DMA0120 / DRG 56x/58x DMA0083 MGCP DRG 11/22 DMA0027 SIP 17

18 DRG SW R2N03-28 Release Notes New Features in DRG SW R2N03-28 No new features are introduced from DRG SW R2N03 to DRG SW R2N28. Resolved issues in DRG SW R2N03-28 The following issues are resolved from DRG SW R2N03 to DRG SW R2N28. Table 2 Bug number Resolved issues Description DRG stops polling when the HDD service stops for period longer than poll interval The DRG stops polling when the HDD service stops for a period longer than the DRG polling interval Phone call does not end after session expire, RFC4208 violation The side not responsible for performing refreshes in a session does not send a BYE to terminate the session when the session expires When call waiting, C can hear conversation from A before call completion In normal start-up mode, no matter whether the connect is sent or not, the DRG starts media immediately when it gets OPENLOGICALCHANNELACK from the peer Issues with the SIP registrations on the F4DRG When the DRG is challenged by the "status : 401 Unauthorised" message with a nonce the same as the one in the previous round of registration, the DRG does not send REGISTER with credentials. This causes DRG re-registration failure The DRG stops sending RTP when there are IGMP queries When the DRG receives IGMP packets, the DRG spends too much time dealing with the packets. This causes the DRG to stop sending RTP packets, and there is a silence for a certain period SIP INFO support for application/dtmf-relay payload DTMF-RELAY is supported as a new DTMF transfer method in this release. DTMF-RELAY can be set as the DTMF transfer method by the KT field in the LxCODECy parameter for a line. The definition for the KT field now is entirely compatible with the previous one and is as follows: 0 - RFC Traditional SIP-INFO 2 - DTMF RELAY 3 - Inbound Set the value of KT field as 2 to enable the DTMF-RELAY method. DTMF-RELAY method can also be enabled by selecting DTMF RELAY as the value for the Keypad box on the Codecs and Fax Configuration page in the DRG Web GUI. Besides, FLASH events can also be sent in DTMF-RELAY method, but the external class 5 service should be enabled to allow the function as well as the above transfer method configuration. 18

19 DRG SW R2N03-28 Release Note Table 2 Bug number Resolved issues Description DRG sends media stream after receiving SIP response with The DRG does not stop sending RTP/RTCP packets when both the following two conditions are true: (1) The DRG has sent re-invite for such reasons as SUSPEND,RESUME or HOLD. (2) The value of connection field of 200OK s SDP for the re-invite is " " SIP URI matching problem Some SIP proxies are non-compliant in request URI. The request URI may be different with URI in the original "Contact" field in the REGISTER request DRG plays DTMF tones endlessly when it receives RTP events with duration values which are not integer times of ten The DRG plays a continuous DTMF tone when it receives a RTP event with a duration value where the last digit is not zero Adding more than one vlan entry by snmp into vlan table failed Only one VLAN can be added into the VLAN table dynamically via SNMP Administering DRG600 Interface via SNMP IF-MIB To enable/disable relevant interfaces, the object drg600aportadmin is added in the port table in the PACKETFRONT-DRG600A-MIB DRG600-Telephony GUI inaccessible The web server is not accessible. But other network applications such as ping and SNMP are not affected. This only happens when IE is used as the web browser. Using Firefox or other web browsers will not cause this problem Unknown SIP message crashes DMA0101-R2N03.R0 Some SIP proxies are non-compliant in their responses to SIP REGISTER requests. Two specific problems are resolved: 1. SIP proxy changes the TO and FROM fields in responses to SIP REGISTER requests. 2. SIP proxy does not include correct tag in the "200 OK" response SIP Update not working in DRG11/22 in R2N The header field "Require: timer" is missing in the 200 OK response to the SIP UPDATE. This causes the peer terminate a connected call. 19

20 DRG SW R2N03-28 Release Notes Known issues in DRG SW R2N28 The following issues are known in DRG SW R2N28. Table 3 Known issues Bug number Discovered Description R2N Parameter values insufficient for COUNTRY param for CLIP Parameter values are insufficient for COUNTRY parameter for CLIP. The parameter value ETSI_DURING_RINGING should be removed, and the following values should be added: 1. ETSI_DURING_DT-AS 2. ETSI_DURING_RP-AS 3. ETSI_DURING_LR+DT-AS R2N TV freezes when multiple STBs are watching the same channel When using multiple STBs connected to DRG560/580, the TV picture may freeze R2N DHCP Option 225 cannot configure SIP server port When using DHCP option 225 for configuring SIP server details, non-default settings for ports are used as the local port, not the SIP server port. Workaround: Always use default ports R2N Echo Cancellation causes loss of voice Under some conditions, when both sides talk, the DRG may stop sending voice traffic for up to 30 seconds. Workaround: Disabling echo cancellation has been shown to stop this issue from occurring R2N H.323: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N H.248: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N DMA0083: DRG stops responding Following configuration changed by HDD, a DRG may become unresponsive and disappear from the network. It must be rebooted to become active again. 20

21 DRG SW R2N03-28 Release Note Table 3 Known issues Bug number Discovered Description R2N Multicast streams do not stop If a multicast client leaves a group without sending a leave message, the multicast stream will not time out and be removed R2N Turning off IGMP Snooping stops all multicast If IGMP snooping is disabled for one port, all multicast traffic flows are stopped and cannot be restarted R2N DMA0027: SIP registration problem after WAN outage If the path between DRG and SIP proxy is interrupted long enough for the registration to expire, then the DRG may fail to register with the proxy when the disruption is removed R2N DMA0027 R2N14 only sends End Event at Flash Hook Flash Hook, enabled either tapping the receiver or using the R button, only produces an RTP Flash End event. Because no Start event packets are sent, the certain External Class 5 service will not work in customer switches R2N SIP stops working after a final REGISTER response matching transaction but not matching dialog If the DRG receives a response to a REGISTER message where the URI does not match the request, the SIP application may stop working R2N H.323: DRG incoming calls failure Incoming H323 calls may fail on DRG R2N Using SNMP to reconfigure access VLANs breaks connection Using SNMP to configure VLANs may cause VLAN configuration to be corrupted R2N Not able to configure ports on DRG600-Access through HDD For the DRG600, it is not possible to configure ports using HDD R2N SNMP get/set not matching configurations On DRG600A, some SNMP objects may not match the actual device configuration. 21

22 DRG SW R2N03-28 Release Notes Table 3 Known issues Bug number Discovered Description R2N Contact-URI is used for CLIP instead of display name The Contact-URI may be used for CLIP information instead of From-URI. Under normal conditions, these values are the same and this has no effect R2N CLIP presentation of number does not work when dial plan contains reverse substitution which includes "+" If the dial plan contains a reverse substitution rule that includes "+", the caller ID value used will not contain the reverse substitution, but will use the value from SIP "from uri" context R2N GUI stops responding after a while after being upgraded to R2N18 The web server is not accessible. But other network applications such as ping and SNMP are not affected R2N No respond to MGCP request when "Max. delay before RSIP" set to 0 If the value of maximum delay before RSIP is set to zero, the DRG will register with the MGCP agent, but will then stop communicating with the agent. Workaround: Use a non-zero value for max delay before RSIP R2N H323 call failes under some complex media capability negotiation condition When the DRG makes calls over H.323, in rare cases some calls might fail due to incompatibility between the DRG and the terminal device on the other end of the call. If the H.245 terminalcapabilityset message received by the DRG contains some unrecognized capabilities in one entry, the DRG cannot negotiate a correct voice codec with the called party and thus fails to send Open Logical Channel (OLC) messages. If the called party happens to be the slave, the called party cannot send Open Logical Channel (OLC) messages either. Both parties hang in OLC waiting status. When timeout occurs, the call fails R2N DRG crashes behind NAT when server side keep-alive is enabled The DRG crashes after receiving approximately 500 OPTION messages with extensions in the "Via" field R2N DRG Web GUI does not support Google Chrome The DRG does not fully support Google Chrome. If the user makes some configuration changes on the GUI using Chrome and restarts the DRG, the configurations are not updated R2N TCP RST on incoming call Sometimes during H.323 call setup, DRG refuses the peer TCP connection, which causes the incoming call failure. 22

23 DRG SW R2N03-28 Release Note Table 3 Known issues Bug number Discovered Description R2N The parameter XML file defines the telephony service twice The DRG parameter XML file that is used by HDD includes duplicate telephony service definitions R2N Busy subscriber handles incoming call incorrectly when internal class5 disabled If a VoIP line is configured in External Class 5 service mode and the line is active in a call, when another call comes in, DRGOS does not provide the 486 Busy message, but replies with a 180 Ringing SIP message. This is because DRGOS has Call Waiting Caller ID (CWCID) enabled and thus sends the CW tone and CID information to the handset R2N sipapp crashes during attended transfer between line 1 and line 2 When a voice call is established between two lines (A and B) on the same DRG, if the callee presses "Flash 4" to transfer the call to C, the SIP application in DRGOS may crash R2N 400 SDP Syntax Error The DRG is unable to process SIP messages that contain "-" in Session Description Protocol (SDP) session attributes, such as "a=x-nat:0" R2N DRG does not respond to ARP queries in which "Sender MAC address" is different from source MAC address If the "Sender MAC address" in an ARP query is different from the source MAC address, the DRG does not respond to this ARP query. 23

24 DRG SW R2N03-28 Release Notes 24

25

26