freeswitch

freeswitch copied to clipboard

Describe the bug

Inbound SIP call to Verto Freeswitch 1.10.7 it's KO

The behavior was correct in freeswitch version 1.10.6 (caller id correct)

To Reproduce Steps to reproduce the behavior:

1. SIP call recieve (inbound call)
2. bridge to verto
3. caller id wrong, (caller ID is same callee ID)
4. the caller's number and caller name is sent correctly on the diplay_name and display_number fields of the verto display after answer

Expected behavior Caller ID must contain the correct number of the caller on verto invite

Package version or git hash

• Version [1.10.7]

Trace logs { "jsonrpc": "2.0", "id": 2182, "method": "verto.invite", "params": { "callID": "166f61e1-53b0-4660-8fde-4b5f75bc165a", "variables": { "Event-Name": "CHANNEL_DATA", "Core-UUID": "7bc7e5cb-5817-4af2-b365-5b01e277acf4", "FreeSWITCH-Hostname": "itmixxxxxx.milano.xxxxxx.yy", "FreeSWITCH-Switchname": "itmixxxxxx.milano.xxxxxx.yy", "FreeSWITCH-IPv4": "138.132.xxx.yyy", "FreeSWITCH-IPv6": "::1", "Event-Date-Local": "2022-06-22 13:56:38", "Event-Date-GMT": "Wed, 22 Jun 2022 13:56:38 GMT", "Event-Date-Timestamp": "1655906198285045", "Event-Calling-File": "switch_channel.c", "Event-Calling-Function": "switch_channel_get_variables_prefix", "Event-Calling-Line-Number": "4502", "Event-Sequence": "44078" }, "sdp": "v=0\r\no=FreeSWITCH 1655889750 1655889751 IN IP4 138.132xxx.xx\r\ns=FreeSWITCH\r\nc=IN IP4 138.132.xxx.xx\r\nt=0 0\r\na=msid-semantic: WMS jYeONq4ygmCcg45IFHFDZUBgRJ2Aidts\r\nm=audio 16448 RTP/SAVPF 0\r\na=rtpmap:0 PCMU/8000\r\na=fingerprint:sha-256 C2:38:74:D7:E5:75:A4:87:0B:A8:ED:92:54:60:23:D0:D9:BD:AF:CE:95:F8:B0:45:44:F9:A5:57:3A:8A:D4:2A\r\na=setup:actpass\r\na=rtcp-mux\r\na=rtcp:16448 IN IP4 138.132.xxx.xx\r\na=ssrc:3605410046 cname:2y6GO15VexXkrTSW\r\na=ssrc:3605410046 msid:jYeONq4ygmCcg45IFHFDZUBgRJ2Aidts a0\r\na=ssrc:3605410046 mslabel:jYeONq4ygmCcg45IFHFDZUBgRJ2Aidts\r\na=ssrc:3605410046 label:jYeONq4ygmCcg45IFHFDZUBgRJ2Aidtsa0\r\na=ice-ufrag:roqg8RnQqfhzjBSc\r\na=ice-pwd:ZOIDGDoK1cViVE5cSljR2wxj\r\na=candidate:2464055862 1 udp 2130706431 138.132.xxx.xx 16448 typ host generation 0\r\na=candidate:2464055862 2 udp 2130706431 138.132.xxx.xx 16448 typ host generation 0\r\na=silenceSupp:off - - - -\r\na=ptime:20\r\na=sendrecv\r\n", "caller_id_name": "52279", "caller_id_number": "52279", "callee_id_name": "52279", "callee_id_number": "52279", "display_direction": "outbound" } }

{ "jsonrpc": "2.0", "id": 36762, "method": "verto.display", "params": { "callID": "0c58f764-726b-4cf9-8897-9b427c7c0c93", "display_name": "3200xxxxxx", "display_number": "3200xxxxxx", "caller_id_name": "52279", "caller_id_number": "52279", "callee_id_name": "52279", "callee_id_number": "52279", "display_direction": "outbound" } }

This is happening to me too. sip_profile bridges to verto users, but the caller number is the same as the user extension.

No way to get the caller number? Running Freeswitch 1.10.7 on Debian 10.

I have the same issue. The fact that the verto.display after the answer sends me the correct caller is too late for me because I need to notify the called during the ringing (verto.invite).

Running Freeswitch 1.10.7

Correct behavior in Freeswitch 1.10.6

Hello, after debugging I noticed that the caller number change occurs at line 2365 of mod_verto.c (freeswitch vers. 1.10.7) .

Before doing this set of variables in the caller_id_number was contained the correct number .

After that line in the caller_id_number is stored the number of the called