@cengbrecht What I would do with this is to do a full TCP dump with rtp, have a google around if you cannot find out how to do it then come back and give us a shout.
Once you have that, at least you can go back then and find out if audio was being sent to/from the PBX at the time that lost audio. This will at least point you in the direction to start looking.
Its possible session timers are coming into play here and contributing to some of the havoc.
I had exactly this issue with my mrs phone. Session timers have been introduced recently and can be a pain.
You can check for this easily in sngrep.
On an outbound call look at the 200OK from Freeswitch:
If this line is present then go into advanced/sip profiles and edit the internal profile. Look for this:
Change it to:
Then flush memcache and restart the internal profile.
Once you have done this, check sngrep again to see that the line has now gone.
That may be enough, good luck
Once you have that, at least you can go back then and find out if audio was being sent to/from the PBX at the time that lost audio. This will at least point you in the direction to start looking.
Its possible session timers are coming into play here and contributing to some of the havoc.
I had exactly this issue with my mrs phone. Session timers have been introduced recently and can be a pain.
You can check for this easily in sngrep.
On an outbound call look at the 200OK from Freeswitch:
Code:
2018/08/22 01:52:40.694169 192.168.1.118:5060 -> 192.168.1.160:12450
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.1.160:5060;branch=z9hG4bK2470559023;rport=12450
From: "Daz" <sip:200@192.168.1.118>;tag=3427536712
To: <sip:*9664@192.168.1.118>;tag=FS912mm3QpK9a
Call-ID: 4_573590978@192.168.1.160
CSeq: 2 INVITE
Contact: <sip:*9664@192.168.1.118:5060;transport=tcp>
User-Agent: FreeSWITCH
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Session-Expires: 120;refresher=uas <------------------------------------------------------------ This could be the problem
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 222
Remote-Party-ID: "*9664" <sip:*9664@192.168.1.118>;party=calling;privacy=off;screen=no
If this line is present then go into advanced/sip profiles and edit the internal profile. Look for this:
Change it to:
Then flush memcache and restart the internal profile.
Once you have done this, check sngrep again to see that the line has now gone.
That may be enough, good luck