I backed up and restored my FreePBX 16 onto a new FreePBX 17. Noticing that when external calls our phone line, reception takes the call and transfers the call to another extension, that callerid is not transferred with the call to the new extension.
Anyone can help to where start looking? I fiddled around with the Trunk/Extension/Advance setting send RPID but doesn’t look like any of the combinations work.
The caller ID should change. I’m now not sure if you are saying that you want the reception caller ID to remain or you want it never to be displayed.
The latter is not possible, as Asterisk doesn’t know that there is a transfer in progress at the time the new destination is rung; as far as it is concerned, it is just a separate call, on the receptionist’s second line. For the former, you would need to disable connected line updates.
At the destination extension (after the call has been transferred), I want that phone to display who is calling (eg. external caller id). Currently it shows the reception is calling and when that person picks up the phone, they are in for a surprise!
Everything was working the way it was intended on FreePBX 16. I did a backup+restore on the new system… Also changed from chan_sip to PJSIP
I think you need to provide a full log, verbosity at least 5, and with “pjsip set logger on” in effect, so we can confirm whether it should be and is sending the update,
The sequence you describe is a native SIP attended transfer, so the initial number displayed will be that of the receptionist, as the call is implemented as an enquiry followed by the actual transfer. One would then need to check whether UPDATE was allowed, and is actually being used.
Asterisk feature code transfer are identifiable as transfers, and will show the external caller ID, from the start.
I would look at the “Extension” level, the issues I’ve usually had going from one PBX version to another has always been something with the extension. I would check these things, you can focus on just the reception extension and a test extension. Trust RPID=Yes, Send Connected Line=Yes, Send RPID=Send P-Asserted-Identity header
I assume you have tried standard IT practices of rebooting server/clients, if not then at least reboot the reception phone and your test phone and do a fwconsole reload on your pbx. You might even go so far as to factory reset a test phone first and let it download it’s config again, then do your reception phone. Or restart the entire pbx this evening. Reboot’s can and do fix things sometimes. Maybe though if you can sanitize your logs and drop them in some pbx guru here can sift through them and find something.
Try setting connnected_line_method to update. I don’t know if this is exposed by FreePBX.
The phone isn’t sending an Allow header, so I don’t think Asterisk can be sure that UPDATE will work, but you need it to work to be able to change connected line on an outgoing leg, before answer.