[ASTPPCOM-849] CLONE - Add select option in did forward always filed. Created: 06/Dec/21  Updated: 21/Sep/22  Resolved: 19/Sep/22

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: v5.0, v4.0.1
Fix Version/s: v5.0

Type: Bug Priority: Highest
Reporter: Prashant Kumar Assignee: Jaimin Solanki (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: 4h 17m
Original Estimate: Not Specified

Attachments: PNG File 4GE5buRW2j.png     PNG File image-2021-12-03-15-05-46-005.png    
Issue Links:
Cloners
Relates
Reproducibility: always
Category: UI
Sprint: 2022-COM-DEV-V60-W37
Edition: Enterprise

 Description   

 

Steps to Reproduce :- 

  1. Login as Admin.
  2. Go to Inbound > DID.
  3. Select any customer and set scenario DID forwarding options "If Busy", "If SIP Not Registered", "If No Answer".
  4. Now Registered SIP devices.
  5. Not dial DID Number. 
  6. Now check DID forwarding options when Busy, Not Registered and No answer.

Actual result :- When first extension is Busy/Not Registered/No answer then it only forwarding on "Always" option. It didn't forward to Busy/Not Registered/No answer option. There is no any option for disable or enable DID forward options.   There is no "select" option here in Did Forward "Always".

Expected result :- 1. When first extension is Busy/Not Registered/No answer then it should be  forward on set DID forward "Busy/Not Registered/No answer" option.

2. There should be options for enable/disable DID forward "Always/Busy/Not Registered/No answer" options.

See Attached videos :- 

 

See Attached latest screenshot :- 

 

Note :- This issue is also in Enterprise v6.0 version W30 container. 

This issue has already fixed in w29 source.

 

Let me know if any concern.

Thank You



 Comments   
Comment by Jaimin Solanki (Inactive) [ 16/Sep/22 ]

The Task is Resolved,

https://gitlab.com/inextrix/ITPLATP/ASTPPCOM/-/merge_requests/776

 

Comment by Prashant Kumar [ 21/Sep/22 ]

verified in latest source betav601,

i have reported new bug for particular sip routing strategies for advance SIP routing, so closing this issue.

Generated at Sat Feb 10 07:20:49 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.