I just installed FreePBX 17. Restored my backup and things are working!
However when I call outbound I get the number I’m calling replaced with “s”
Confirmed with both Bria and the Yealink T48 on my desk.
Edit: This is just the display on the phone or app that shows “s” where the number I’m calling should be.
And my trunk is Flowroute if that matters. Trunk config worked fine in SNG7 and is unchanged.
jcolp
(Joshua Colp)
June 24, 2024, 9:53pm
3
There is already an open Github issue here:
opened 02:18PM - 17 Jun 24 UTC
bug
needs-information
### FreePBX Version
FreePBX 17
### Issue Description
im unable to pin down th… e update that triggered the issue however with any outbound call to the PSTN phones are now displaying 's' and i don't recall this during any testing last week and only noticed it today. this impacts all makes of phones...
note this entry in the attached log ...
**_<sip:[email protected] >_**
as well as the **_'s'_** displayed below the caller ID
examples of phone displays with this error in place on both S series and P series
![main-screen](https://github.com/FreePBX/issue-tracker/assets/2153999/e107be85-438c-488f-8126-9862ccdc5543)
![Screenshot 2024-06-17 at 7 23 45 AM](https://github.com/FreePBX/issue-tracker/assets/2153999/f77c537b-2a92-4fe7-80e0-0c4033167b4a)
### Operating Environment
+---------------------+------------+---------+-------------+-----------+
| Module | Version | Status | License | Signature |
+---------------------+------------+---------+-------------+-----------+
| accountcodepreserve | 17.0.0.1 | Enabled | GPLv2 | Sangoma |
| amd | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| announcement | 17.0.2.1 | Enabled | GPLv3+ | Sangoma |
| api | 17.0.1.4 | Enabled | AGPLv3+ | Sangoma |
| areminder | 17.0.3.10 | Enabled | Commercial | Sangoma |
| arimanager | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| asterisk-cli | 17.0.2 | Enabled | GPLv3+ | Sangoma |
| asteriskinfo | 17.0.2 | Enabled | GPLv3+ | Sangoma |
| backup | 17.0.5.48 | Enabled | GPLv3+ | Sangoma |
| blacklist | 17.0.1.2 | Enabled | GPLv3+ | Sangoma |
| broadcast | 17.0.1.6 | Enabled | Commercial | Sangoma |
| builtin | | Enabled | | Unsigned |
| bulkhandler | 17.0.4 | Enabled | GPLv3+ | Sangoma |
| calendar | 17.0.4.14 | Enabled | GPLv3+ | Sangoma |
| callaccounting | 17.0.5 | Enabled | Commercial+ | Sangoma |
| callback | 17.0.2.1 | Enabled | GPLv3+ | Sangoma |
| callerid | 17.0.1 | Enabled | Commercial | Sangoma |
| callforward | 17.0.1.6 | Enabled | AGPLv3+ | Sangoma |
| calllimit | 17.0.1.2 | Enabled | Commercial | Sangoma |
| callrecording | 17.0.3.6 | Enabled | AGPLv3+ | Sangoma |
| callwaiting | 17.0.3.4 | Enabled | GPLv3+ | Sangoma |
| cdr | 17.0.4.15 | Enabled | GPLv3+ | Sangoma |
| cdrpro | 17.0.3.16 | Enabled | Commercial | Sangoma |
| cel | 17.0.2.8 | Enabled | GPLv3+ | Sangoma |
| certman | 17.0.3.11 | Enabled | AGPLv3+ | Sangoma |
| cidlookup | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| conferences | 17.0.3.2 | Enabled | GPLv3+ | Sangoma |
| conferencespro | 17.0.1.7 | Enabled | Commercial | Sangoma |
| configedit | 17.0.1.1 | Enabled | AGPLv3+ | Sangoma |
| contactmanager | 17.0.5.11 | Enabled | GPLv3+ | Sangoma |
| core | 17.0.9.68 | Enabled | GPLv3+ | Sangoma |
| cos | 17.0.1.1 | Enabled | Commercial | Sangoma |
| customappsreg | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| dashboard | 17.0.4.3 | Enabled | AGPLv3+ | Sangoma |
| daynight | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| dictate | 17.0.1.2 | Enabled | GPLv3+ | Sangoma |
| directory | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| disa | 17.0.3 | Enabled | AGPLv3+ | Sangoma |
| donotdisturb | 17.0.2.3 | Enabled | GPLv3+ | Sangoma |
| endpoint | 17.0.1.70 | Enabled | Commercial | Sangoma |
| extensionroutes | 17.0.1 | Enabled | Commercial | Sangoma |
| extensionsettings | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| fax | 17.0.3.4 | Enabled | GPLv3+ | Sangoma |
| faxpro | 17.0.1.15 | Enabled | Commercial | Sangoma |
| featurecodeadmin | 17.0.2 | Enabled | GPLv3+ | Sangoma |
| filestore | 17.0.2.20 | Enabled | AGPLv3 | Sangoma |
| findmefollow | 17.0.4.8 | Enabled | GPLv3+ | Sangoma |
| firewall | 17.0.1.26 | Enabled | AGPLv3+ | Sangoma |
| framework | 17.0.15.27 | Enabled | GPLv2+ | Sangoma |
| hotelwakeup | 17.0.1.6 | Enabled | GPLv2 | Sangoma |
| iaxsettings | 17.0.1 | Enabled | AGPLv3 | Sangoma |
| infoservices | 17.0.1 | Enabled | GPLv2+ | Sangoma |
| ivr | 17.0.6 | Enabled | GPLv3+ | Sangoma |
| languages | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| logfiles | 17.0.3.3 | Enabled | GPLv3+ | Sangoma |
| manager | 17.0.5 | Enabled | GPLv2+ | Sangoma |
| miscapps | 17.0.3 | Enabled | GPLv3+ | Sangoma |
| miscdests | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| missedcall | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| music | 17.0.4 | Enabled | GPLv3+ | Sangoma |
| outroutemsg | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| paging | 17.0.3 | Enabled | GPLv3+ | Sangoma |
| pagingpro | 17.0.1.6 | Enabled | Commercial | Sangoma |
| parking | 17.0.2.4 | Enabled | GPLv3+ | Sangoma |
| parkpro | 17.0.1.4 | Enabled | Commercial | Sangoma |
| pbxmfa | 17.0.2 | Enabled | Commercial+ | Sangoma |
| phpinfo | 17.0.1 | Enabled | GPLv2+ | Sangoma |
| pinsets | 17.0.3.2 | Enabled | GPLv3+ | Sangoma |
| pinsetspro | 17.0.2 | Enabled | Commercial | Sangoma |
| pm2 | 17.0.3.2 | Enabled | AGPLv3+ | Sangoma |
| presencestate | 17.0.2.4 | Enabled | GPLv3+ | Sangoma |
| printextensions | 17.0.1.2 | Enabled | GPLv3+ | Sangoma |
| queueprio | 17.0.1.4 | Enabled | GPLv3+ | Sangoma |
| queues | 17.0.1.9 | Enabled | GPLv2+ | Sangoma |
| queuestats | 17.0.1.7 | Enabled | Commercial | Sangoma |
| qxact_reports | 17.0.2 | Enabled | Commercial | Sangoma |
| recording_report | 17.0.3.8 | Enabled | Commercial | Sangoma |
| recordings | 17.0.2.2 | Enabled | GPLv3+ | Sangoma |
| restapps | 17.0.1.18 | Enabled | Commercial | Sangoma |
| ringgroups | 17.0.2.4 | Enabled | GPLv3+ | Sangoma |
| sangomaconnect | 17.0.1.34 | Enabled | Commercial | Sangoma |
| sangomacrm | 17.0.1.5 | Enabled | Commercial | Sangoma |
| sangomartapi | 17.0.1.25 | Enabled | Commercial | Sangoma |
| setcid | 17.0.1.2 | Enabled | GPLv3+ | Sangoma |
| sipsettings | 17.0.6.7 | Enabled | AGPLv3+ | Sangoma |
| sipstation | 17.0.3.3 | Enabled | Commercial | Sangoma |
| sms | 17.0.1.13 | Enabled | Commercial | Sangoma |
| smsplus | 17.0.3 | Enabled | Commercial | Sangoma |
| soundlang | 17.0.4.1 | Enabled | GPLv3+ | Sangoma |
| sysadmin | 17.0.1.88 | Enabled | Commercial | Sangoma |
| timeconditions | 17.0.1.17 | Enabled | GPLv3+ | Sangoma |
| tts | 17.0.1.1 | Enabled | GPLv3+ | Sangoma |
| ttsengines | 17.0.1 | Enabled | AGPLv3 | Sangoma |
| ucp | 17.0.4.18 | Enabled | AGPLv3+ | Sangoma |
| userman | 17.0.6.25 | Enabled | AGPLv3+ | Sangoma |
| vmblast | 17.0.2 | Enabled | GPLv3+ | Sangoma |
| vmnotify | 17.0.1.7 | Enabled | Commercial | Sangoma |
| voicemail | 17.0.5.19 | Enabled | GPLv3+ | Sangoma |
| voicemail_report | 17.0.1.1 | Enabled | Commercial | Sangoma |
| voipinnovations | 17.0.1.4 | Enabled | Commercial | Sangoma |
| vqplus | 17.0.1.16 | Enabled | Commercial | Sangoma |
| weakpasswords | 17.0.1 | Enabled | GPLv3+ | Sangoma |
| webcallback | 17.0.4 | Enabled | Commercial | Sangoma |
| webrtc | 17.0.2.2 | Enabled | GPLv3+ | Sangoma |
+---------------------+------------+---------+-------------+-----------+
### Relevant log output
```shell
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.250.170:5060;rport=9521;received=73.121.231.224;branch=z9hG4bKadcbffd
Call-ID: [email protected]
From: "1301" <sip:[email protected] >;tag=75221d971cc3420
To: <sip:[email protected] >;tag=30102018-c0f3-4740-a784-d45bb9c043ca
CSeq: 21 INVITE
Server: FPBX-17.0.15.27(21.0.2)
Allow: OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, REFER
Contact: <sip:45.79.206.42:5060>
P-Asserted-Identity: "CID:4236504818" <sip:[email protected] >
Content-Type: application/sdp
Content-Length: 246
```
That has been escalated to the Asterisk team to investigate since it seems to be some sort of interaction between Gosub and FreePBX usage.
2 Likes
Awesome… glad to know it’s not just me
kgupta
(Kapil Gupta)
June 25, 2024, 3:31am
5
For the time being , quick work around could be to set Trust RPID =NO and Send Connected Line=NO on your extension’s PJSIP advanced setting and give a try.
Thanks Kapil, that worked perfectly.
Do you have Send PAI off? Because it didnt work for me.
Send PAI is set to no on my Flowroute trunk (unchanged from SNG7 config).
kgupta
(Kapil Gupta)
July 18, 2024, 6:35am
10
Hello everyone,
We have addressed the issue where an incorrect display number was being shown when the “send connected line” feature was enabled.
For more details on the root cause and fixes implemented, please visit GitHub Issue #313 .
We kindly request you to enable the “send connected line” parameter (and ensure Trust RPID is set to Yes) and test it with the latest FreePBX 17 core version 17.0.10.
Thank you for your cooperation.
Best regards,
Kapil
Updated and confirmed fixed! Thank you!
system
(system)
Closed
July 25, 2024, 6:43pm
12
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.