search

team-telnyx / telnyx-webrtc-android

Telnyx Android WebRTC SDK - Enable real-time communication with WebRTC and Telnyx
MIT License
13 stars 2 forks source link

[Bug] Incomming call invitation contains wrong number #312

Closed Del-S closed 9 months ago

Del-S commented 1 year ago

Bug Category

SDK Version implementation 'com.github.team-telnyx:telnyx-webrtc-android:v1.2.21-alpha'

Describe the bug I called from SIM (Czech Republic) into Telnyx SDK and I received a call invitation with wrong number.

Expected behaviour Invitation should contain proper number.

To Reproduce Steps to reproduce the behaviour:

  1. Login to telnyx.
  2. Receive call invitation.

Android Device (please complete the following information):

Logs

So after many days of testing and trying i came across a "funny" issue. I am calling to the app (in emulator) from my physical device located in Czech Republic with international prefix +420. I tried around like 300 calls and this is the first time it happened. I received an invitation with number +1420732652757 instead of +420732652757.

ReceivedMessageBody(method=telnyx_rtc.invite, result=InviteResponse(callId=f961737a-a1b6-49a9-92f1-089ef6b9c1a0, sdp=v=0
    o=FreeSWITCH 1688975097 1688975098 IN IP4 185.246.41.178
    s=FreeSWITCH
    c=IN IP4 185.246.41.178
    t=0 0
    a=msid-semantic: WMS lVXXbovBYpnSyWzILtEYIMlKxS8PJn6U
    m=audio 19622 RTP/SAVPF 0 8
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=fingerprint:sha-256 2F:4D:84:66:34:F1:23:CB:A4:B1:84:72:FC:4D:01:1E:2F:24:9F:1F:3A:C4:93:CC:F0:BD:11:DC:19:70:5A:AE
    a=setup:actpass
    a=rtcp-mux
    a=rtcp:19622 IN IP4 185.246.41.178
    a=ssrc:2360085743 cname:8TI983BWiOFHA4fc
    a=ssrc:2360085743 msid:lVXXbovBYpnSyWzILtEYIMlKxS8PJn6U a0
    a=ssrc:2360085743 mslabel:lVXXbovBYpnSyWzILtEYIMlKxS8PJn6U
    a=ssrc:2360085743 label:lVXXbovBYpnSyWzILtEYIMlKxS8PJn6Ua0
    a=ice-ufrag:oK1WncxKVvpuIlfG
    a=ice-pwd:5NG3G8QPMlndgtgu37hhaERV
    a=candidate:9346008219 1 udp 2130706431 185.246.41.178 19622 typ host generation 0
    a=candidate:9346008219 2 udp 2130706431 185.246.41.178 19622 typ host generation 0
    a=silenceSupp:off - - - -
    a=ptime:20
    a=sendrecv
    , callerIdName=+1420732652757, callerIdNumber=+1420732652757, sessid=8658e246-ab00-4a79-9cd2-1bfa205232c9)

Seems like an edge case but it might happen.

Del-S commented 1 year ago

Note that it seems that another number received the call. I was calling the number +1 217-225-9201 but it seems that it also triggered a call on +1 217-225-9604.

isaacakakpo1 commented 10 months ago

@Del-S I believe this was a backend implementation issue. Is this resolved now ?

Del-S commented 9 months ago

Seems to be fine now. It happened sporadically but it seems to be okay now.