PJSIP trunk configurations are filtering video CODECs ( H264 , VP8 etc) outbound.
I see the Video Codecs being forwarded by my soft client to the server and I have H264 & VP8 enabled under the Asterisk SIP settings configuration, as well as in the extension allowed field; however,
the GUI settings for the PJSIP trunk group ( CODECS ) are filtering the video CODECS from the INVITE request.
The INVITE forwarded from the server will conform to any CODEC settings defined for the PJSIP trunk group; but there appears to be no settings defined here to allow any video CODECs.
Does anyone know if there’s a work around for this???
I don’t speak for the company or the brand, but soon isn’t too soon. The chan-sip code is old and is no longer actively maintained. No new features have been added in years and everything ‘stupid’ that ChanSIP used to do exclusively is now “mostly” supported in PJ-SIP. It’s almost a full replacement for ChanSip and as soon as no one can find any more edge cases, it will go away.
I don’t think the issue here is with pjsip as much as that video seems to be more of an afterthought in FreePBX. I don’t blame anyone for this as FreePBX was not designed as a video platform; it was designed as a PBX.
There are other tickets in place for video options enhancements.
I agree with cynjut’s assessment. I would use pjsip and just disable the chan_sip driver. If you happen to find a case that only chan_sip can solve, you can enable it (and file a ticket with FreePBX or Asterisk to let them know).
Again, I thoroughly appreciate your time and assistance. My initial testing was performed with chanSIP configurations in place ( endpoints / trunks etc) and there were no issues with the transmission and reception of voice or video. So, If there was a definitive timeline ( lets say 3-5 years) for the EOL support of ChanSIP configurations, I could possibly continue with my testing as is/was.
Regardless, I’ll take the information you’ve provided to heart, and will continue with the conversion from a ChanSIP to PJSIP PBX environment - thanks again for the assist.
btw - G-Poob/GPB1 is just fine (What can I say, I loved watching the Flintstones when I was kid).
FreePBX isn’t Asterisk. It’s more like a management framework for Asterisk. Asterisk will get full support for video codecs long before FreePBX will, even though Digium and Sangoma are now the same commercial entity. It’s open source software, so if there’s things we want added, we need to add them.
I’ve only ever donated one thing to the project, and it was adopted “sideways”. I wrote an SCCP Manager (back in the 1.6 days) and added some Report changes for Chan-SCCP support (lines, devices, etc.) so that you could look at Asterisk Info at a glance and get the scoop. Rather than adopt my singular changes, they decided to modify Asterisk Info so that more modules (Chan-GSM is a thing, after all) could report information through the AsteriskInfo module.
That’s how a lot of this stuff gets into the system. You need it, you make it happen, a couple other people like it and help it move forward, and eventually it gets support in FreePBX. The SCCP Manager program is now in someone else’s portfolio (mine is still out there, but please don’t look) and it fully supports the current version of FreePBX. They really took it and ran with it in ways I could never afford to.
In other words, if you can figure out how to make something happen and provide code to make it happen, it’s a lot more likely that your “single person” change will make it into the system.
I used to code in Mesozoic languages like COBOL, RPG, FORTRAN & PASCAL in the 80’s but gave that up in the 90’s. I’d be completely lost if I tried my hand @ any of the newer languages (C# / C++ / JAVA) etc, but will need to wait for one of you geniuses to make that happen.
If you can do any work in Pascal, you should be able to grind your way through PHP. They’re pretty close. It’s not like we’re building the phone systems with format statements in column 8 or dropping 77-levels into the logic.