[ASTPPCOM-1146] Advance SIP routing :- "On Busy" SIP routing is not working, displaying error in fs_cli logs. Created: 20/Sep/22  Updated: 11/Oct/22  Resolved: 11/Oct/22

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: v6.0
Fix Version/s: v6.0

Type: Bug Priority: High
Reporter: Prashant Kumar Assignee: Ashish Gohil
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 43m
Original Estimate: Not Specified

Attachments: File On_Busy_SIP_sip_routing.mp4    
Issue Links:
Relates
relates to ASTPPCOM-983 Advance SIP Routing[Backend] Done
Reproducibility: always
Category: Call
Edition: Community

 Description   

Steps :-

  1. Login as admin.
  2. installed advance SIP Routing add on.
  3. now login as admin/reseller/customer.
  4. go to SIP devices > and create at least 3 SIP devices, For Ex :- 111, 222, 333,
  5. Now click on advance option of any one sip device (for ex of 111).
  6. now enable "On Busy" routing type and select any one SIP device (222) and save.
  7. now registered above SIP devices.
  8. now Dial DID-local or SIP2SIP call and observe as per set scenario.

Actual result :- "On Busy" SIP routing is not working, displaying error in fs_cli logs.

Expected result :-  "On Busy" SIP routing should be working  fine, and call should be route on selected sip device.

See Fs_CLI logs and videos :- https://pastebin.freeswitch.org/view/6419d3e5 

 

 Comments   
Comment by Ashish Gohil [ 20/Sep/22 ]

This issue is resolved in ASTPPCOM-983.

Comment by Prashant Kumar [ 11/Oct/22 ]

verified in latest source community v6.0

change applied done, working fine as expected.

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