Closed tongsoftinfo closed 2 years ago
Hi @tongsoftinfo is this issue still happening?
If so, can you please provide a recent call ID and Session ID or a snippet of the invitation socket message from logcat?
call_control_id 7177e3d2-e816-11ec-8ec5-02420a0d8168 call_session_id 7177ec10-e816-11ec-b316-02420a0d8168
@tongsoftinfo has this happened in the last 3 days? I am asking because I believe this was a temporary backend issue that has since been resolved.
If this has happened in the 3 days, please provide the invite socket message as mentioned earlier.
eg:
[TxSocket] Receiving [{"jsonrpc":"2.0","id":3350,"method":"telnyx_rtc.invite","params":{"callID":"4039c9b3-d4d2-4c5d-8d4c-438f022912b0","variables":{"Event-Name":"CHANNEL_DATA","Core-UUID":"bf576b48-d172-419f-9d66-77462ba1f398","FreeSWITCH-Hostname":"b2bua-rtc.tel-ld6-ibm-prod-138","FreeSWITCH-Switchname":"b2bua-rtc.tel-ld6-ibm-prod-138","FreeSWITCH-IPv4":"10.31.15.80","FreeSWITCH-IPv6":"::1","Event-Date-Local":"2022-06-13 08:50:15","Event-Date-GMT":"Mon, 13 Jun 2022 08:50:15 GMT","Event-Date-Timestamp":"1655110215154946","Event-Calling-File":"switch_channel.c","Event-Calling-Function":"switch_channel_get_variables_prefix","Event-Calling-Line-Number":"4576","Event-Sequence":"15713"},"sdp":"v=0\r\no=FreeSWITCH 1655085091 1655085092 IN IP4 185.246.41.164\r\ns=FreeSWITCH\r\nc=IN IP4 185.246.41.164\r\nt=0 0\r\na=msid-semantic: WMS OBv16CjeLiwpjaTRrefEB8avTPDxtZa8\r\nm=audio 25124 RTP/SAVPF 102 0 8\r\na=rtpmap:102 opus/48000/2\r\na=fmtp:102 useinbandfec=1; maxaveragebitrate=30000; maxplaybackrate=48000; ptime=20; minptime=10; maxptime=40; stereo=1\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=fingerprint:sha-256 4C:D2:BD:3A:E7:90:32:54:15:77:8F:AE:D4:A2:7A:49:A2:B7:38:98:08:7F:03:FD:82:08:97:D7:73:9A:37:B1\r\na=setup:actpass\r\na=rtcp-mux\r\na=rtcp:25124 IN IP4 185.246.41.164\r\na=ssrc:4205298327 cname:rwZnY8rAhOQqPA86\r\na=ssrc:4205298327 msid:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8 a0\r\na=ssrc:4205298327 mslabel:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8\r\na=ssrc:4205298327 label:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8a0\r\na=ice-ufrag:EdB6cBrVhVjALky2\r\na=ice-pwd:GngumyVucBKR1JOwNgsPIKBP\r\na=candidate:6933238806 1 udp 2130706431 185.246.41.164 25124 typ host generation 0\r\na=candidate:6933238806 2 udp 2130706431 185.246.41.164 25124 typ host generation 0\r\na=silenceSupp:off - - - -\r\na=ptime:20\r\na=sendrecv\r\nm=video 25126 RTP/SAVPF 105\r\nb=AS:1024\r\na=rtpmap:105 VP8/90000\r\na=mid:video\r\na=sendrecv\r\na=fingerprint:sha-256 4C:D2:BD:3A:E7:90:32:54:15:77:8F:AE:D4:A2:7A:49:A2:B7:38:98:08:7F:03:FD:82:08:97:D7:73:9A:37:B1\r\na=setup:actpass\r\na=rtcp-mux\r\na=rtcp:25126 IN IP4 185.246.41.164\r\na=rtcp-fb:105 ccm fir\r\na=rtcp-fb:105 ccm tmmbr\r\na=rtcp-fb:105 nack\r\na=rtcp-fb:105 nack pli\r\na=ssrc:3377765067 cname:rwZnY8rAhOQqPA86\r\na=ssrc:3377765067 msid:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8 v0\r\na=ssrc:3377765067 mslabel:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8\r\na=ssrc:3377765067 label:OBv16CjeLiwpjaTRrefEB8avTPDxtZa8v0\r\na=ice-ufrag:8yosVCPKsTpQCrSs\r\na=ice-pwd:LAPGKSWu0a0CdNWbcauYD9yV\r\na=candidate:0188578318 1 udp 2130706431 185.246.41.164 25126 typ host generation 0\r\na=candidate:0188578318 2 udp 2130706430 185.246.41.164 25126 typ host generation 0\r\na=end-of-candidates\r\n","caller_id_name":"test","caller_id_number":"35315227159","callee_id_name":"NAME","callee_id_number":"OliverZimmerman8","telnyx_session_id":"d7cfca14-eaf5-11ec-8681-02420a1f0d69","telnyx_leg_id":"d7d4ac5a-eaf5-11ec-9c10-02420a1f0d69","display_direction":"outbound"}}]
Also to confirm:
Android phone A makes a call to Android phone B. Android phone B receives the invitation and accepts Android phone A does not receive an answer socket message, and instead receives BYE after a wait time
call_control_id
12ec84b8-ea2c-11ec-b5b0-02420a0d8868
call_session_id
12ec91a6-ea2c-11ec-a4c4-02420a0d8868
call_control_id
80f2e62a-e881-11ec-b5de-02420a0d4168
call_session_id
80f2f872-e881-11ec-bed7-02420a0d4168
This is the information from a few days ago
@tongsoftinfo can you confirm if the scenario explained above is correct and whether it has happened again recently? If it hasn't happened within the last few days I would close this issue (as a resolved backend issue) and reopen it if it happens again with the relevant information (invite socket message)
This problem has indeed appeared in the last few days, but due to the condition of the phone, we are currently not logging invite socket messages.
Can you please plugin the other phone and grab the invite from logcat? Is it only happening on one specific device? Has it happened again today?
We do not have such information at this time, and if there is, we will record it
The MediaPlayer is used in TelnyxClient.kt, but there is no mediaPlayer.release() in the method stopMediaPlayer, only mediaPlayer.stop() and mediaPlayer.reset(), so that the MediaPlayer does not end the release, is this correct?
2022年8月2日 16:28,zhangjun @.***> 写道:
The MediaPlayer is used in TelnyxClient.kt, but there is no mediaPlayer.release() in the method stopMediaPlayer, only mediaPlayer.stop() and mediaPlayer.reset(), so that the MediaPlayer does not end the release, is this correct?
Bug Category
SDK Version
implementation 'com.github.team-telnyx:telnyx-webrtc-android:v1.2.12-alpha'
Describe the bug
After making a call, the webhook receives the answering information, but the mobile phone does not receive the corresponding answering information, and has been waiting to answer. After some time the phone receives telnyx_rtc.bye status information but not telnyx_rtc.answer status information
Expected behaviour Make a call, when the webhook receives the connection status, it can immediately notify the mobile phone
To Reproduce Enter the number, click to dial, wait to answer
Android Device (please complete the following information):