******************************************************** Release Notes - Vega 400 R8.8 S027 ******************************************************** No New Features No Changed Features Ref / ID Title / Summary Version - Engineer / Testing REDMINE 8062 T.38 With 3CX Not Working R8.8 026 Kapil Gupta T38 Max buffer and T38 Max datagram size was not matching with 3CX expectations due to which 3CX was rejecting T.38 Reinvite from Vega. Added CLI for above attributes so that we can change the value on-the-fly. No Known Problems ******************************************************** Release Notes - Vega 400 R8.8 S026 ******************************************************** No New Features No Changed Features No Bug Fixes No Known Problems ******************************************************** Release Notes - Vega 400 R8.8 S025 ******************************************************** No New Features No Changed Features Bug Fixes Ref / ID Title / Summary Version - Engineer / Testing REDMINE 8090 ID 1246 MFCR2 Argentina: The default settings does not work with the Telecom Argentina R8.8 025 Mark Lewington Default for 'end_of_ani' and 'no_ani_to_send' changed from '12' to '15' for profile 3 (Argentina)in dslcfg.c REDMINE 8088 ID 1247 Vega fails to work with an autoattend of Hperpbx Asterisk System R8.8 025 Mark Lewington Interworking timing issue between R2 and SIP. The 200 is being processed before Forward tone II has been received causes incorrect backward tone to be sent resulting in call failure. SIPp script using varying pause before 200 sent (with and without 183). No Known Problems ******************************************************** Release Notes - Vega 400 R8.8 S024 ******************************************************** No New Features No Changed Features Bug Fixes Ref / ID Title / Summary Version - Engineer / Testing REDMINE 7613 ID 1243 Vega unable to handle received fragmented UDP packets R8.8 024 Trevor Harwood The Vega firewall routes packets based on UDP port number. Second and subsequent packet fragments do not have a port number so the packet gets dropped. Forced a PC to have an MTU of 700. Send a SIP INVITE which exceeded 700 octets so that the packet is fragmented. Vega SIP stack receives and responds to the packet. REDMINE 7408 ID 1244 Ticket#9147 - Registration User Name Limited to 31 Characters R8.8 024 Mark Lewington Additional fix required to increase array dimension to 63 chars. REDMINE 8251 ID 1245 Vega200 (InConcert) not able to make more than 25 outbound calls R8.8 024 Mark Lewington In a call from SIP to R2 where there is a forward clear received by the R2 call leg in the ‘cas_outgoing’ state (before connect), theR2 stack does not report a disconnect billing event to call management. This means that the billing handle in call context does not get released by the R2 call leg, therefore call context for this call never gets released back to the pool. Tested using 2 Vegas connected with R2 back to back and fired 1000 calls in each direction. The Vega with the fix lost 0 call context handles whereas the other Vega without the fix lost 53 handles. REDMINE 8090 ID 1246 MFCR2 Argentina: The default settings does not work with the Telecom Argentina R8.8 025 Mark Lewington Default for 'end_of_ani' and 'no_ani_to_send' changed from '12' to '15' for profile 3 (Argentina)in dslcfg.c REDMINE 8088 ID 1247 Vega fails to work with an autoattend of Hperpbx Asterisk System R8.8 025 Mark Lewington Interworking timing issue between R2 and SIP. The 200 is being processed before Forward tone II has been received causes incorrect backward tone to be sent resulting in call failure. SIPp script using varying pause before 200 sent (with and without 183). No Known Problems ******************************************************** Release Notes - Vega 400 R8.8 S023 ******************************************************** No New Features No Changed Features Bug Fixes Ref / ID Title / Summary Version - Engineer / Testing REDMINE 7387 ID 1238 [Broadsoft] SDP version -> increment R8.8 023 Mark Lewington Increment the SDP version number for this specific case Broadsoft testcase when we are responding to a re-invite with no SDP. This is not really necessary as we don't change the SDP but I don't think it can do any harm and avoids a customer specific config parameter. Tested by Rob Pereira during Broadsoft testing REDMINE 7406 ID 1239 [Broadsoft] SIP Registration expires timeout not being respected R8.8 023 Trevor Harwood Add handling for Min-Expires header and 423 SIP_INTERVAL_TOO_BRIEF Response. Tested by Rob Pereira during Broadsoft testing. REDMINE 7408 ID 1240 Ticket#9147 - Registration User Name Limited to 31 Characters R8.8 023 Mark Lewington Increase length of "sip.reg.user.X.dn" and "sip.reg.user.X.username" to 63 chars. REDMINE 5784 ID 1241 ENP - no option to configure ITSP Proxy Test timeout R8.8 023 Mark Lewington Further fix to detect failed Options ping more quickly. Vega will now expect a response to Options ping within 50% of the configured ping interval. Previously the response time was hard-coded to 30seconds. REDMINE 7435 ID 1242 The vega50 BRI should include "27" as its default Causes Codes in Re-Presentation Group R8.8 023 Trevor Harwood Added cause 27 to the list of cause codes for re-presentation group 99 in Quick Config. Verified that cause 27 is added to the list of cause codes. REDMINE 7613 ID 1243 Vega unable to handle received fragmented UDP packets R8.8 024 Trevor Harwood The Vega firewall routes packets based on UDP port number. Second and subsequent packet fragments do not have a port number so the packet gets dropped. Forced a PC to have an MTU of 700. Send a SIP INVITE which exceeded 700 octets so that the packet is fragmented. Vega SIP stack receives and responds to the packet. REDMINE 7408 ID 1244 Ticket#9147 - Registration User Name Limited to 31 Characters R8.8 024 Mark Lewington Additional fix required to increase array dimension to 63 chars. REDMINE 8251 ID 1245 Vega200 (InConcert) not able to make more than 25 outbound calls R8.8 024 Mark Lewington In a call from SIP to R2 where there is a forward clear received by the R2 call leg in the ‘cas_outgoing’ state (before connect), theR2 stack does not report a disconnect billing event to call management. This means that the billing handle in call context does not get released by the R2 call leg, therefore call context for this call never gets released back to the pool. Tested using 2 Vegas connected with R2 back to back and fired 1000 calls in each direction. The Vega with the fix lost 0 call context handles whereas the other Vega without the fix lost 53 handles. No Known Problems