Hello everyone,

Does anyone have any insight into how 'SIMPLE MESSAGE' delivery can be achieved between sip and verto clients? The verto documentation is very light on detail especially when it comes to messaging. There are references to using chat in conferences but that's about it.

I've tried appending the protocol in the "to" value ( ie. "verto+9905@voip.gh.bf" ) but that doesn't appear to help much. It does change the to_proto to verto, but the message doesn't end up being delivered to the verto client. Any help would be greatly appreciated.

-Matthew

On 3/21/2018 3:03 PM, Matthew Grooms wrote:

Hello All,

We have a few hundred agents on a custom built call center platform that leverages freeswitch and mod_callcenter. Up until now, agents have used a custom built Windows Client based on pjsip. I'm trying to replace that with a new client built with WebRTC and mod_verto. The last piece of the puzzle I'm trying to solve is sending chat messages between Verto and SIP clients. I can use the chat command from fs_cli to send messages to freeswitch to a Verto client, but I can't seem to send messages from a SIP client to a Verto client or a Verto client to a SIP client. After spending a few days on this, I thought I'd appeal to the list to see if someone can help provide some guidance.

# show registrations
reg_user,realm,token,url,expires,network_ip,network_port,network_proto,hostname,metadata
1000,voip.gh.bf,0d5831a1b9274063a1e06237f47a68af,sofia/external/sip:1000@X.X.X.X:49524;transport=TCP;ob,1521650573,X.X.X.X,49524,tcp,voip2.gh.bf,

# verto status
                     Name Type                                       Data      State
=================================================================================================
                     mine       profile ws:0.0.0.0:8081      RUNNING
                     mine       profile wss:0.0.0.0:8082      RUNNING
    mine::9905@voip.gh.bf       client X.X.X.X:60992      CONN_REG (WSS)
=================================================================================================
1 profile , 1 client


Messages are delivered when I try the following ...

CHAT TO VERTO:
-------------------- CONSOLE --------------------
# chat verto|1000@voip.gh.bf|9905@voip.gh.bf|test
2018-03-21 11:20:48.170147 [ALERT] mod_verto.c:604 WRITE X.X.X.X:49548 [{
        "jsonrpc":      "2.0",
        "id":   6,
        "method":       "verto.info",
        "params":       {
                "msg":  {
                        "from": "1000@voip.gh.bf",
                        "to":   "9905@voip.gh.bf",
                        "body": "test"
                }
        }
}]
-------------------- CHROME --------------------
onVertoMessage from:1000@voip.gh.bf to:9905@voip.gh.bf body:test


Messages are not delivered when trying to send from client to client ...

SIP TO VERTO:
-------------------- EVENT --------------------
KV -> Chat-Send-From: "A" <sip:1000@voip.gh.bf>;tag=759225c356d545d2b8c83b284063cac2
KV -> Chat-Send-Profile: external
KV -> Chat-Send-To: 9905@voip.gh.bf
KV -> Content-Length: 4
KV -> Core-UUID: 74a1329b-6a85-4078-9c0d-f9af5972bf0a
KV -> Error-Reason: no recipient
KV -> Error-Type: chat
KV -> Event-Calling-File: sofia_presence.c
KV -> Event-Calling-Function: sofia_presence_chat_send
KV -> Event-Calling-Line-Number: 276
KV -> Event-Date-GMT: Wed, 21 Mar 2018 15:44:13 GMT
KV -> Event-Date-Local: 2018-03-21 10:44:13
KV -> Event-Date-Timestamp: 1521647053570639
KV -> Event-Name: CUSTOM
KV -> Event-Sequence: 299577
KV -> Event-Subclass: sofia::error
KV -> FreeSWITCH-Hostname: voip2.gh.bf
KV -> FreeSWITCH-IPv4: X.X.X.X
KV -> FreeSWITCH-IPv6: ::1
KV -> FreeSWITCH-Switchname: voip2.gh.bf
-------------------- CONSOLE --------------------
2018-03-21 10:44:13.570639 [WARNING] sofia_presence.c:221 Not sending to local box for 9905@voip.gh.bf
2018-03-21 10:44:13.570639 [ERR] sofia_presence.c:272 Chat proto [sip]
from ["A" <sip:1000@voip.gh.bf>;tag=759225c356d545d2b8c83b284063cac2]
to [9905@voip.gh.bf]
test
Nobody to send to: Profile external

VERTO TO SIP:
-------------------- EVENT --------------------
KV -> Content-Length: 22
KV -> Core-UUID: 74a1329b-6a85-4078-9c0d-f9af5972bf0a
KV -> Event-Calling-File: mod_verto.c
KV -> Event-Calling-Function: verto__info_func
KV -> Event-Calling-Line-Number: 3374
KV -> Event-Date-GMT: Wed, 21 Mar 2018 15:50:56 GMT
KV -> Event-Date-Local: 2018-03-21 10:50:56
KV -> Event-Date-Timestamp: 1521647456550625
KV -> Event-Name: MESSAGE
KV -> Event-Sequence: 299780
KV -> FreeSWITCH-Hostname: voip2.gh.bf
KV -> FreeSWITCH-IPv4: X.X.X.X
KV -> FreeSWITCH-IPv6: ::1
KV -> FreeSWITCH-Switchname: voip2.gh.bf
KV -> Nonblocking-Delivery: true
KV -> dest_proto: GLOBAL
KV -> from: 9905@voip.gh.bf
KV -> from_full: 9905
KV -> from_host: voip.gh.bf
KV -> from_user: 9905
KV -> proto: verto
KV -> to: 1000@voip.gh.bf
KV -> type: text/plain
KV -> verto_jsock_uuid: 85eef9c8-54c2-f4a7-eb95-ef9f5f1e6ff8
KV -> verto_profile: mine
-------------------- CONSOLE --------------------
freeswitch@voip2.gh.bf> 2018-03-21 10:50:56.550625 [ALERT] mod_verto.c:1384 READ X.X.X.X:64275 [{
        "jsonrpc":      "2.0",
        "method":       "verto.info",
        "params":       {
                "msg":  {
                        "to":   "1000@voip.gh.bf",
                        "from": "9905@voip.gh.bf",
                        "body": "This is a test message"
                },
                "sessid": "85eef9c8-54c2-f4a7-eb95-ef9f5f1e6ff8"
        },
        "id":   5
}]
2018-03-21 10:50:56.550625 [ALERT] mod_verto.c:604 WRITE X.X.X.X:64275 [{
        "jsonrpc":      "2.0",
        "id":   5,
        "result":       {
                "message":      "SENT",
                "sessid": "85eef9c8-54c2-f4a7-eb95-ef9f5f1e6ff8"
        }
}]

Thanks in advance,

-Matthew