Why would MySQL be preferable to PostgreSQL anyway? FusionPBX will install it all for you - and even take backups of that database? If you want to add some integrations, every language has PostgreSQL (be sure to integrate against custom views, not against the tables directly!)
They are still targeting Debian 8 as their platform of choice. There's still plenty of life left in Debian 8 - although personally i just run FusionPBX in its own container.
^0[012378][0-9]{9}$
Which means 0 at the start, then one of 012378, then nine of 0-9, then the end
I dont really understand whats wanted with the 44, but here is is with 44 on the front
^440[012378][0-9]{9}$
My expectation was that setting sip_cid_type=pid and/or caller-id-type=pid - would impact both A and B leg. Thats not the case.
Also sip_cid_in_1xx is entirely independant of the above.
On reflection is probably for the best that they only impact on leg, as you may have different handsets, so...
The section i added above is very very close. $callee_id_name is not the right variable. im struggling to find what variable holds the original caller number on the phone calling the park+*5901 to retrieve the park.
if i set it to some text, that text will show up on the phone retrieving the...
setting sip_cid_type=pid and/or caller-id-type=pid seems to only affect the B-leg (the person being called i.e. the callee)
the A leg seems to always receive remote-party-id in 183 responses. the above two settings seem to have no impact. The sip_cid_in_1xx variable turns remote-party-id...
Although im not using Polycom, the SIP traces im getting show that its not returning a RPID or PID header with the original callers number.
From the Active Calls screen in FusionPBX, it seems that FreeSWITCH still knows what the callers number retrieved from park is.
So what im trying to do is...