early RTP issue? Cutting first few digit at the initial incoming call.

[youthtelco]

Avaya SM 8/0, IP-phone J159 SIP

My client said that they’ve been using the special website to get a verification code. When they login that website with their credentials, they could get a call to their phone from the site that the code is delivered over a phone. For some reason as of yesterday, the phone rings then gets last 2 digit code of the 6 digit code. Other normal call is fine. Other college who uses that site is also on same issue. Does anyone have any idea or recommendation about this? Trace looks like same with others.


15:20:47 TRACE STARTED 01/23/2024 CM Release String cold-01.0.890.0-26095
15:28:23 Calling party trunk-group 999 member 7 cid 0x1b4d
15:28:23 Calling Number & Name 12345678 NO-CPName
15:28:23 dial 1305
15:28:23 term station 1305 cid 0x1b4d
15:28:23 dial 1305
15:28:23 term trunk-group 997 cid 0x1b4e
15:28:23 dial 1305
15:28:23 route-pattern 49 preference 1 location ALL cid 0x1b4e
15:28:23 seize trunk-group 997 member 92 cid 0x1b4e
15:28:23 Calling Number & Name 12345678 NO-CPName
15:28:23 INVITE going via Sig Grp 910, ignoring called number routing
15:28:23 SIP>INVITE sip:1305@test.com SIP/2.0
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 Setup digits 1305
15:28:23 Calling Number & Name 12345678 NO-CPName
15:28:23 SIP<SIP/2.0 100 Trying
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 Proceed trunk-group 997 member 92 cid 0x1b4e
15:28:23 SIP<INVITE sip:1305@test.com SIP/2.0
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP>INVITE sip:1305@test.com SIP/2.0
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP<SIP/2.0 100 Trying
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP>SIP/2.0 100 Trying
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP<SIP/2.0 180 Ringing
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP>SIP/2.0 180 Ringing
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 SIP<SIP/2.0 180 Ringing
15:28:23 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:23 ring station 1305 cid 0x1b4d
15:28:23 Alert trunk-group 997 member 92 cid 0x1b4e
15:28:23 Alerting party uses private-numbering
15:28:25 SIP<SIP/2.0 200 OK
15:28:25 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:25 SIP>SIP/2.0 200 OK
15:28:25 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:25 SIP<SIP/2.0 200 OK
15:28:25 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:25 SIP>ACK sip:1305@172.17.48.155:24855;transport=tcp;gsid=f4a
15:28:25 SIP>3a062-ba2d-41ee-97c4-000c29df7964;asm=3;epv=%3Csip:1305
15:28:25 SIP>%40test.com%3Bgr%3Dcc4ebedd4294b91aa2dcf2bd7ceaf48
15:28:25 SIP>4%3E SIP/2.0
15:28:25 Call-ID: f4a3a92cba2d41ee97c70c29df7964
15:28:25 active station 1305 cid 0x1b4d
15:28:25 Connected party uses private-numbering
15:28:26 SIP>BYE sip:1305@172.17.48.155:24855;transport=tcp;gsid=f4a
15:28:26 SIP>3a062-ba2d-41ee-97c4-000c29df7964;asm=3;epv=%3Csip:1305
15:28:26 SIP>%40test.com%3Bgr%3Dcc4ebedd4294b91aa2dcf2bd7ceaf48
15:28:26 SIP>4%3E SIP/2.0
15:28:26 Call-ID: f4a3a92cba2d41ee97c70c29df7964