[ASTPPCOM-1382] if we set Outbound Caller ID translation in customer, then after dialed direct PSTN number, caller id didn't changed as per applied localization. Created: 10/Aug/23 Updated: 25/Sep/23 Resolved: 19/Sep/23 |
|
| 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: | 8h 58m | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Reproducibility: | always |
| Category: | Call |
| Sprint: | 2023-COM-DEV-V70-W33 |
| Edition: | Community |
| Description |
|
Steps :-
Actual result :- if we set Outbound Caller ID translation in customer, then after dialed direct PSTN number, caller id didn't changed as per applied localization. Expected result :- if we set Outbound Caller ID translation in customer, then after dialed direct PSTN number, then it should be changed as per applied localization. See Attached Videos or fs_cli log :- https://pastebin.freeswitch.org/view/057ce84b Note :- Same thing working fine when dialed PSTN number through Calling card feature as per fixed in
|
| Comments |
| Comment by Ashish Gohil [ 19/Sep/23 ] |
|
This issue is resolved, changes done as per comment, outbound calls localization not working for caller id. PR |
| Comment by Prashant Kumar [ 25/Sep/23 ] |
|
Verified in latest source Community V6.0 Change applied done, now working fine as expected. |