I just took my desktop T38 and forced g722 on a PJSIP extension. Dialed *43 and it worked fine. I can post the video if someone really needs me to do so.
Can you please factory reset those phones, and do not do anything else apart from setting the username, password, and server? Donāt provision them, donāt do anything. Just log into the GUI, enter those three things, and then try *43.
I have got the same issues here. I upgraded my FreePBX Distro to V13 with Asterisk 13.5 - all updates are installed.
In the past, I was using chan_sip to connect to my endpoints and trunks and everything was fine. For testing purposes, I changed some extensions to use pjsip. And thatās when all got odd. Itās the same as described here. Internal calls between to pjsip extensions using G722 work just fine - but when it gets to playback of internal audio files like announcements, there is just silence. Iāve tested with different extensions and different endpoints. My Yealink T38G, my Grandstream GXV3175v2 and my Siemens Gigaset VoIP DECT Phone. All the same. All have worked properly with chan_sip, but they donāt do with chan_pjsip - as long as you use G722 as voice codec. Only my Aastra 6755i seemed working as it should.
I then figured out a mysterious behavior: In the phone configs, I had set the phones to may use multiple voice codecs. G722, alaw and gsm (as I live in Germany), while the G722 codec came in the first place, as ist should be prefered. I removed all codecs except the G722 in the phone configuration. Believe it or not, that did it. All phones now were playing the audio files.
Of course this is not a solution, because I still want the phones to be able to use a branch of codecs, as they did, when using chan_sip. For me, there are still issues, that make me return to chan_sip. Thatās because, my trunks use chan_sip with alaw as codec, and with pjsip endpoints external calls only ring 10 seconds and then break down - but are displayed and handled as answered. I think, this might also have something to do with the codec or the transcoding.
So, if you ask me: I donāt think we have an FreePBX related issue here. It also isnāt phone related, because ist happens on multiple endpoints. In deed, only my Aastra Phones seem to have no problems even when multiple codecs are selected. What we have here seems to be a problem with the chan_pjsip driver.
Oh, by the way: I followed your tip, Rob. Factory reset and just registering the phones didnāt change anything.
Perhaps my āencountersā help to solve the problem.
Ran into this issue today. 3 of my 4 endpoints would only get silence when playing g722 system recordings. At some point it magically started working and have been unable to recreate. As far as I can tell, the only thing I did that might have fixed was:
Were you being sarcastic on your last post? Sorry, I am really in doubt.
I can give access to my FreePBX box that has this problem. If anyone wants to log in and take a look, be my guest. What I need is the IP address of the person loggin in and the public ssh key (contents of the .ssh/id_rsa.pub file).
I can open ports 22/tcp, 5060/udp and 10000-20000/udp, temporarily and only to the IP address informed.
By the way, the problem happens for me both on Yealink and on Grandstream phones (I only tested these 2 brands).
Well, maybe someone from FreePBX side would be interested in digging a bit, even if to get it fixed on Asterisk? If some Asterisk expert can take a look at it and open a ticket it will have better chances of being worked on.
If I go to Asterisk community and say I have a one-way audio problem with G722 they will call me crazy just like happened here
I know Andrew and Rob both were able to get this to work. But I am curious, in your testing, did you:
Go to Settings ā> Asterisk SIP Settings and enable the g722 codec and make it the top priority?
Or did you go to the extension settings page, enter āallā in āDisallowed Codecsā, and enter āg722ā in āAllowed Codecsā?
If you tested with method 2, it will work every time. 2 way audio with the PBX will work without any issue using the g722 codec. But, if you use method 1, it has failed for me every time in my testing. Thus, it seems possible that this is a FreePBX issue, not an Asterisk issue. Asterisk is obviously able to transcode properly, because method 2 above works fine.
If you can prove that itās a configuration issue we are all willing to fix it (Obviously). But we canāt duplicate and if we canāt duplicate then we canāt be expected to fix it (because how would we know what to do).
Please stop pointing the blame on FreePBX unless you can prove (through configurations) that it is the problem. Otherwise we keep going in circles.
Andrew - Read my post again. In fact, let me quote, italicize and place in bold the part you missed:
No need to be a jerk. Iām not pointing blame at FreePBX. Iām trying to figure it out, along with the other 6 people in this thread that have experienced the same problem. Because you canāt duplicate it, you are the one insisting it is an Asterisk issue. In fact, I had dropped the issue due to your confrontational nature in participating in this thread. But, as additional users continue to experience the problem, it pops back up on my radar and I look into it a little further.
Now that we have addressed that, you still didnāt answer my question in my last post. Let me remind you:
Iām not sure how you tested, but if you watch Robās video here, you will see that he tested using method #2 from my post:
Myself and others have confirmed that it works fine if forcing the g722 codec from the extensions page. However, since you havenāt answered the question, you have not proved that you duplicated the scenario I proposed as Method #1.
Please forgive me for using the Open Source FreePBX Distro and using itās community forum for seeking help with a problem I experienced usingā¦ the FreePBX Distro. In fact, the whole nature the community exploded right after we purchased some Commercial Modules. The whole FreePBX/Sangoma vs Ward Mundy debate started, and the Sangoma Community Forum became much more confrontational and condescending. Letās just say that it didnāt take long for me to start questioning the wisdom of where we spent our money.
Since I am not a developer, I obviously do not approach such matters the same as you would. I simply donāt have the experience or focused expertise you possess as a developer. But, my troubleshooting skills have shown me that Asterisk can transcode properly. (See Robās video.) But, by configuring Asterisk, using FreePBX, with two different approaches to using the g722 codec, you get different results. In my simple mind, these results donāt isolate FreePBX or Asterisk as the source of the problem. I apologize that I have used the Sangoma/FreePBX āCommunity Forumsā for discussion, rather than strict issue reporting.
Would it be possible to get a straight answer about your approach to testing this issue? Did you force the g722 codec on the extension page? If so, you, myself and others (including Rob in his video) confirm it works, just as you insist. However, there are about 6 people (excluding any Sangoma/FreePBX developers or support staff) that have experienced this problem while configuring FreePBX by going to the āSettings -----> Asterisk SIP Settingsā in FreePBX, enabling the g722 codec, then making it the top priority. Using this method of configuration, we (at least 6 FreePBX users) experience one way audio.
I hope you are able to understand my frustration with the confrontational reply I received and are able to simply answer my question, rather than accuse me of any ill intent.
I am sad that you think this has anything to do with me and how I deal with responses and tickets. In fact this is the only thread I have participated in with you. Being a jerk can go both ways. I think you will agree looking back at this thread.