Jump to content

execcomm

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by execcomm

  1. Any fix? I tried version 68 and it has problem too.
  2. I am also experinencing the same problem. But mine is 3.5.3 and the server is 67.0.6. I was working before.
  3. This is what telnyx replies: Additionally could you explain in a little more detail why you're trying to set up a TCP connection, as my colleague explained this is generally something we would handle on our side? If you're sending the message through our API the POST is made by us therefore there's no need for you to open a connection. To test this you can send a test message using cURL based on the guide in our developer docs here: https://developers.telnyx.com/docs/v2/messaging/quickstarts/sending-sms-and-mms
  4. Yes, it's on the list. I download it, and check it against the certificate and it matches 100% Telnyx say that everything is working ok with telnyx sms server, and they cannot check anymore without the exact code that sends the pbx. I tried sending the log, but say that is insufficient data.
  5. Not working by pressing the reset button.
  6. Was able to wireshark and this is: Frame 828: 167 bytes on wire (1336 bits), 167 bytes captured (1336 bits) on interface 0 Ethernet II, Src: Cisco, Dst: Juniper Internet Protocol Version 4, Src: 192.168.1.100, Dst: 192.76.120.28 Transmission Control Protocol, Src Port: 3149, Dst Port: 443, Seq: 1, Ack: 1, Len: 113 Source Port: 3149 Destination Port: 443 [Stream index: 18] [TCP Segment Len: 113] Sequence number: 1 (relative sequence number) [Next sequence number: 114 (relative sequence number)] Acknowledgment number: 1 (relative ack number) 0101 .... = Header Length: 20 bytes (5) Flags: 0x018 (PSH, ACK) Window size value: 256 [Calculated window size: 65536] [Window size scaling factor: 256] Checksum: 0xc35f [unverified] [Checksum Status: Unverified] Urgent pointer: 0 [SEQ/ACK analysis] TCP payload (113 bytes) Secure Sockets Layer TLSv1.2 Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.2 (0x0303) Length: 108 Handshake Protocol: Client Hello Frame 829: 61 bytes on wire (488 bits), 61 bytes captured (488 bits) on interface 0 Ethernet II, Src: Juniper, Dst: Cisco Internet Protocol Version 4, Src: 192.76.120.28, Dst: 192.168.1.100 Transmission Control Protocol, Src Port: 443, Dst Port: 3149, Seq: 1, Ack: 114, Len: 7 Source Port: 443 Destination Port: 3149 [Stream index: 18] [TCP Segment Len: 7] Sequence number: 1 (relative sequence number) [Next sequence number: 8 (relative sequence number)] Acknowledgment number: 114 (relative ack number) 0101 .... = Header Length: 20 bytes (5) Flags: 0x018 (PSH, ACK) Window size value: 501 [Calculated window size: 64128] [Window size scaling factor: 128] Checksum: 0x3261 [unverified] [Checksum Status: Unverified] Urgent pointer: 0 [SEQ/ACK analysis] TCP payload (7 bytes) Secure Sockets Layer TLSv1.2 Record Layer: Alert (Level: Fatal, Description: Handshake Failure) Content Type: Alert (21) Version: TLS 1.2 (0x0303) Length: 2 Alert Message
  7. Followed the guide to install Telnyx, and I'm having problems. Upgraded to the latest version. 67.6 [8] 12:20:45.323 REST: POST /rest/user/testext@192.168.1.100/chat?number=%2B471675864 {"type":"text","text":"This is a test SMS","date":1629217244810} [6] 12:20:45.325 Could not read file chat\356.xml (error code ERROR_FILE_NOT_FOUND) [8] 12:20:45.326 Using system settings for SMS provider telnyx and user [8] 12:20:45.326 REST: Return 200 Ok (application/json) true [7] 12:20:45.327 https:sms.telnyx.com:443: DNS A returned 192.76.120.28 [7] 12:20:45.327 https:sms.telnyx.com:443: Connect to 192.76.120.28 [9] 12:20:45.341 https:sms.telnyx.com:443: Send request (209 bytes) POST https://sms.telnyx.com/messages HTTP/1.1 Host: sms.telnyx.com x-profile-secret: **************** Content-Type: application/json Content-Length: 64 {"from":"+482612144","to":"+471675864","body":"This is a test SMS"} [9] 12:20:45.341 Initialize TLS connection [9] 12:20:45.341 HTTP 192.76.120.28: Send Client Hello(0303611B..00020017) [5] 12:20:45.355 HTTP 192.76.120.28: Alert Fatal (2): Handshake failure (40) [7] 12:20:45.355 https:sms.telnyx.com:443: TCP disconnect [7] 12:20:45.355 https:sms.telnyx.com:443: Return code 500 [8] 12:20:45.355 https:sms.telnyx.com:443: Return content (0 bytes) [7] 12:20:45.356 Closing connection https:sms.telnyx.com:443
  8. Yes. I set permission to monitor ACDs under Permission of extension tab. Then I log in with that account, and I click on ACD. After that, I click on Missed calls, and I see this.
  9. This is annoying my client a lot. Cannot be used very well with agent groups. Any fix? I'm using a T56A.
  10. It was a problem with telnyx. they fixed it and started working.
  11. When an agent misses a call it just shows up as blank. The buttons under the date also do not work.
  12. Software version67.0.5 (Win64) Build dateMay 6 2021 15:09:05 Tried with Chrome and the Vodia app 3.5.5 Both do the same thing
  13. Yes, me having a same problem. I did not know how to check. Any fix?
  14. Hi, Mine is still not working. 1. I cannot erase the iinformation i put in the first time. If I replace it, the interface resets and goes back and disregards the new info I entered. 2. It doesn't sync. It says "Saved". The contacts don't appear in the in my address book.
  15. Hi, Sorry for the late reply. Now even outgoing is not working. [9] 13:15:21.704 Request /rest/user/765@pbx.local.com/chat?number=%2B17025932233ⓘ POST /rest/user/765@pbx.local.com/chat?number=%2B17025932233 HTTP/1.1 Host: pbx.local.com Connection: keep-alive Content-Length: 56 Accept: */* Accept-Encoding: gzip, deflate, br Accept-Language: en-US Content-Type: application/json; charset=utf-8 Cookie: session=xonvj9c4dels4gzjm1sm Origin: localhost User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) VodiaPBX/3.5.5 Chrome/ Electron/4.2.12 Safari/537.36 [9] 13:15:21.704 Last message repeated 2 timesⓘ [8] 13:15:21.704 REST: POST /rest/user/765@pbx.local.com/chat?number=%2B17025932233ⓘ {"type":"text","text":"hello moto","date":1618334122010} [6] 13:15:21.705 Could not read file chat\266.xml (error code ERROR_FILE_NOT_FOUND)ⓘ [8] 13:15:21.707 Using system settings for SMS provider telnyx and user ⓘ [8] 13:15:21.707 Last message repeated 2 timesⓘ [8] 13:15:21.707 REST: Return 200 Ok (application/json)ⓘ true [7] 13:15:21.707 https:sms.telnyx.com:443: DNS A returned 192.76.120.28ⓘ [7] 13:15:21.707 https:sms.telnyx.com:443: Connect to 192.76.120.28ⓘ [9] 13:15:21.722 https:sms.telnyx.com:443: Send request (208 bytes)ⓘ POST https://sms.telnyx.com/messages HTTP/1.1 Host: sms.telnyx.com x-profile-secret: **************** Content-Type: application/json Content-Length: 63 {"from":"+17022502582","to":"+17025932233","body":"hello moto"} [9] 13:15:21.722 Initialize TLS connectionⓘ [9] 13:15:21.722 HTTP 192.76.120.28: Send Client Hello(..00020017)ⓘ [9] 13:15:21.739 HTTP 192.76.120.28: Receive Server Hello(..03000102)ⓘ [9] 13:15:21.739 HTTP 192.76.120.28: Receive Certificate(..21165953)ⓘ [9] 13:15:21.739 HTTP 192.76.120.28: Received chain with 2 certificatesⓘ [8] 13:15:21.740 HTTP 192.76.120.28: Certificate name *.telnyx.com matchesⓘ [9] 13:15:21.740 HTTP 192.76.120.28: Receive Server Key Exchange(03001741..4221DB5F)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Pre Master Secret(9466BA2A..FDE4358B)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Client Random(..43FBA0C5)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Server Random(..41662906)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Master Secret(..48C05556)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Receive Server Hello Done()ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Send Client Key Exchange(..64BB2363)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Send Change Cipher Spec(01)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Perform Change Cipher Spec(c014)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Key Block(..E061A75D)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Client Write MAC Secret(..127B4B3C)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Server Write MAC Secret(..CAD5E339)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Client Write Key(..E719AF5C)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Server Write Key(..A86AE93A)ⓘ [9] 13:15:21.747 HTTP 192.76.120.28: Send Finished(..F1987F0C)ⓘ [9] 13:15:21.762 HTTP 192.76.120.28: Receive Change Cipher Spec(01)ⓘ [9] 13:15:21.763 HTTP 192.76.120.28: Receive Process Finished(..1A1EB376)ⓘ [9] 13:15:21.798 Received 496 bytesⓘ HTTP/1.1 400 Bad Request Content-Type: application/json; charset=utf-8 Content-Length: 284 Date: Tue, 13 Apr 2021 17:15:21 GMT Server: Python/3.7 aiohttp/3.6.2 Strict-Transport-Security: max-age=15552000 [7] 13:15:21.798 https:sms.telnyx.com:443: Return code 400ⓘ Content-Type: application/json; charset=utf-8 Content-Length: 284 Date: Tue, 13 Apr 2021 17:15:21 GMT Server: Python/3.7 aiohttp/3.6.2 Strict-Transport-Security: max-age=15552000 [8] 13:15:21.798 https:sms.telnyx.com:443: Return content (284 bytes)ⓘ { "code": "40305", "success": false, "status": 400, "message": "The 'from' address should be string containing a valid phone number or alphanumeric sender ID associated with the sending messaging profile.", "url": "https://developers.telnyx.com/docs/overview/errors/40305"
  16. Do not think that Twilio and Telnyx are related. But Telnyx still doesnt work on the 67 version. Works well on the previous version. Is there an update for fix?
  17. Just to inform again. This was working in the previous version. When it says to Tried to match recvsms it gets that logo sutff everytime. Turning everything to 0, and only script and IVR events to 9 does not show any logs. Turning everything to 9, then I get the same thing again: [9] 9:44:41.882 Request /recvsms (I WEBSERVER) POST /recvsms HTTP/1.1 Host: 142.132.6.111 X-Telnyx-Signature: t=162393481,h=uqxssdadsasd2zxc9CqSfKaswxfrw88BulI= Content-Type: application/json Accept: */* Accept-Encoding: gzip, deflate User-Agent: Python/3.7 aiohttp/3.6.2 Content-Length: 150 [7] 9:44:41.882 Provisioning without domain context (I PROV) [9] 9:44:41.882 Tried to match recvsms (I WEBSERVER) logo-320x240.jpg logo-480x272.jpg logo-800x480.jpg aastra.cfg startup.cfg 0c1105######.cfg ale_cert.pem config.############.xml auerswald.xml auerswald-phone-############.xml 46xxsettings.txt 46xxdevice.txt J100Supgrade.txt logo-cisco1.png cisco_softkeys.xml snom_bg820-############.tar snom_bg870-############.tar csc############.pem csc############.cfg cyberdata-############.xml 00268B######.xml fanvil-############.xml fanvil-sysconf.xml fanvil-############.txt fanvil.txt logo-fanvil1.bmp logo-fanvil2.bmp logo-fanvil3.bmp logo-fanvil4.bmp ############.boot flyingvoice.cfg 42/2/master.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg000b82###### cfgc074ad###### cfg.xml cfg/cfg001fc1######.xml cfg001fc1######.xml Alert1.wav Alert10.wav Alert2.wav Alert3.wav Alert4.wav Alert5.wav Alert6.wav Alert7.wav Alert8.wav Alert9.wav provisioning.xml logo-mitel-h1.png logo-mitel-h2.png logo-mitel-h3.png logo-mitel-i1.png logo-mitel-i2.png logo-mitel-i3.png Htek.xml cfg001fc1###### cfg00??.xml factory####.bin KX-UTG200B.cfg KX-UTG300B.cfg KX-UT113.cfg KX-UT123.cfg KX-UT133.cfg KX-UT136.cfg KX-UT1363.cfg KX-UT248.cfg KX-UT670.cfg logo-polycom1.jpg logo-polycom2.jpg logo-polycom3.jpg polycom/############-directory.xml polycom/############-all.cfg polycom/############-app.log ############-app.log polycom/############-app.log ############-boot.log polycom/############-boot.log ############.cfg SEP############.cnf.xml SIPDefault.cnf SIP############.cnf F00786######.flag F00786######.cfg logo-snom1.png logo-snom2.png logo-snom3.png logo-snom4.png snom300-############.htm snom320-############.htm snom360-############.htm snom370-############.htm snom_3xx_dialplan_empty.xml snom_3xx_dialplan_row2.xml snom_3xx_dialplan_row3.xml snom_3xx_dialplan_row4.xml snom_3xx_dialplan_usa2.xml snom_3xx_dialplan_usa3.xml snom_3xx_dialplan_usa4.xml snom_3xx_phone-############.xml snom710-############.htm snom_710_phone-############.xml snom720-############.htm snom_720_phone-############.xml snom_745_phone-############.xml snom760-############.htm snom_760_phone-############.xml snom_785_phone-############.xml snom820-############.htm snom821-############.htm snom_820_phone-############.xml snom870-############.htm snom_branding-############.xml snom_buttons-############.xml C520-WiMi.cfg snom_cert-############.xml snom_firmware-############.xml snomM?00KLE.htm snomM?00SC.htm snomM?00.htm snom-m9-############.xml snom-m9-firmware-############.xml snom-m9-settings-############.xml snom_models-############.xml snomMP-############.htm snom300.htm snom320.htm snom360.htm snom370.htm snom820.htm snom821.htm snom870.htm snomMP.htm snomPA1.htm snomPA1-############.htm snom_thumb-############.jpg snom715-############.htm snom725-############.htm snom765-############.htm snomD120-############.htm snomD305-############.htm snomD315-############.htm snomD335-############.htm snomD345-############.htm snomD375-############.htm snomD385-############.htm snomD712-############.htm snomD715-############.htm snomD717-############.htm snomD725-############.htm snomD735-############.htm snomD745-############.htm snomD765-############.htm snomD785-############.htm snom_v10_phone-############.xml /spa9##.cfg spa############.cfg IP????_############.cfg Temporis_IP????_############.cfg V?????_############.cfg vop_data.xml vop.xml 00a859######.cfg vtech_branding-############.xml vtech_buttons-############.xml vtech_cert-############.xml VTechET605-############.htm VTechET635-############.htm VTechET685-############.htm vtech_firmware-############.xml vtech_models-############.xml ############.cfg vtech_phone-############.xml logo-yealink1.png logo-yealink2.png logo-yealink3.png logo-yealink4.png logo-yealink5.png yealink_cert.pem 001565######.cfg 805e0c######.cfg 805ec0######.cfg yealink-############.cfg yealink.cfg yealink-favorite.xml yealink_mcast.xml yealink-webitem.cfg [8] 9:44:41.882 Receive SMS (I WEBSERVER) {"sms_id": "0c5ccfad-bfd8-4s32-a38b-1be9dasd3b8a6", "direction": "inbound", "from": "+32487730xyz", "to": "+32487730xyz", "body": "This is a 3rd test"} [8] 9:44:42.110 Last message repeated 2 times (SIP)
  18. Disabled web server I am checking under the extension that has the phone number attached to it. If I mouse over the recvsms i icon, it says PROV. Disabling Prov in the logs, no longer shows any messages in regards to any SMS.
  19. Here is the log, i tried several times but that logo stuff keeps on popping up. [9] 13:04:35.836 Accept connection 60 from 192.76.120.11ⓘ [9] 13:04:35.836 Request /recvsmsⓘ POST /recvsms HTTP/1.1 Host: 142.132.6.111 X-Telnyx-Signature: t=234234234,h=9VJHY77U0qLF/wDZWjHa/cqqyqP4D8= Content-Type: application/json Accept: */* Accept-Encoding: gzip, deflate User-Agent: Python/3.7 aiohttp/3.6.2 Content-Length: 150 [7] 13:04:35.836 Provisioning without domain contextⓘ [9] 13:04:35.836 Tried to match recvsmsⓘ logo-320x240.jpg logo-480x272.jpg logo-800x480.jpg aastra.cfg startup.cfg 0c1105######.cfg ale_cert.pem config.############.xml auerswald.xml auerswald-phone-############.xml 46xxsettings.txt 46xxdevice.txt J100Supgrade.txt logo-cisco1.png cisco_softkeys.xml snom_bg820-############.tar snom_bg870-############.tar csc############.pem csc############.cfg cyberdata-############.xml 00268B######.xml fanvil-############.xml fanvil-sysconf.xml fanvil-############.txt fanvil.txt logo-fanvil1.bmp logo-fanvil2.bmp logo-fanvil3.bmp logo-fanvil4.bmp ############.boot flyingvoice.cfg 42/2/master.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg000b82###### cfgc074ad###### cfg.xml cfg/cfg001fc1######.xml cfg001fc1######.xml Alert1.wav Alert10.wav Alert2.wav Alert3.wav Alert4.wav Alert5.wav Alert6.wav Alert7.wav Alert8.wav Alert9.wav provisioning.xml logo-mitel-h1.png logo-mitel-h2.png logo-mitel-h3.png logo-mitel-i1.png logo-mitel-i2.png logo-mitel-i3.png Htek.xml cfg001fc1###### cfg00??.xml factory####.bin KX-UTG200B.cfg KX-UTG300B.cfg KX-UT113.cfg KX-UT123.cfg KX-UT133.cfg KX-UT136.cfg KX-UT1363.cfg KX-UT248.cfg KX-UT670.cfg logo-polycom1.jpg logo-polycom2.jpg logo-polycom3.jpg polycom/############-directory.xml polycom/############-all.cfg polycom/############-app.log ############-app.log polycom/############-app.log ############-boot.log polycom/############-boot.log ############.cfg SEP############.cnf.xml SIPDefault.cnf SIP############.cnf F00786######.flag F00786######.cfg logo-snom1.png logo-snom2.png logo-snom3.png logo-snom4.png snom300-############.htm snom320-############.htm snom360-############.htm snom370-############.htm snom_3xx_dialplan_empty.xml snom_3xx_dialplan_row2.xml snom_3xx_dialplan_row3.xml snom_3xx_dialplan_row4.xml snom_3xx_dialplan_usa2.xml snom_3xx_dialplan_usa3.xml snom_3xx_dialplan_usa4.xml snom_3xx_phone-############.xml snom710-############.htm snom_710_phone-############.xml snom720-############.htm snom_720_phone-############.xml snom_745_phone-############.xml snom760-############.htm snom_760_phone-############.xml snom_785_phone-############.xml snom820-############.htm snom821-############.htm snom_820_phone-############.xml snom870-############.htm snom_branding-############.xml snom_buttons-############.xml C520-WiMi.cfg snom_cert-############.xml snom_firmware-############.xml snomM?00KLE.htm snomM?00SC.htm snomM?00.htm snom-m9-############.xml snom-m9-firmware-############.xml snom-m9-settings-############.xml snom_models-############.xml snomMP-############.htm snom300.htm snom320.htm snom360.htm snom370.htm snom820.htm snom821.htm snom870.htm snomMP.htm snomPA1.htm snomPA1-############.htm snom_thumb-############.jpg snom715-############.htm snom725-############.htm snom765-############.htm snomD120-############.htm snomD305-############.htm snomD315-############.htm snomD335-############.htm snomD345-############.htm snomD375-############.htm snomD385-############.htm snomD712-############.htm snomD715-############.htm snomD717-############.htm snomD725-############.htm snomD735-############.htm snomD745-############.htm snomD765-############.htm snomD785-############.htm snom_v10_phone-############.xml /spa9##.cfg spa############.cfg IP????_############.cfg Temporis_IP????_############.cfg V?????_############.cfg vop_data.xml vop.xml 00a859######.cfg vtech_branding-############.xml vtech_buttons-############.xml vtech_cert-############.xml VTechET605-############.htm VTechET635-############.htm VTechET685-############.htm vtech_firmware-############.xml vtech_models-############.xml ############.cfg vtech_phone-############.xml logo-yealink1.png logo-yealink2.png logo-yealink3.png logo-yealink4.png logo-yealink5.png yealink_cert.pem 001565######.cfg 805e0c######.cfg 805ec0######.cfg yealink-############.cfg yealink.cfg yealink-favorite.xml yealink_mcast.xml yealink-webitem.cfg [8] 13:04:35.836 Receive SMSⓘ {"sms_id": "eb4e415c-79d9-432bd-91fd-3c23dddebde5", "direction": "inbound", "from": "+32487730xyz", "to": "+32487730xyz", "body": "This is just simple test"}
  20. Hi, thanks for the response. But it's on the extension, not on the ACD. Again, this was working perfectly fine before upgrading to 67.0
  21. I can send messages from my extension but cannot receive. It was working good before. I did not modify anything since. [9] 11:01:37.744 Tried to match recvsms [8] 11:01:37.744 Receive SMS {"sms_id": "129xxxxx32232848ba", "direction": "inbound", "from": "+xxxxxxxxxx", "to": "+xxxxxxxxxx", "body": "Testing 123"} Using the app or the desktop interface, nothing shows. The number is added under the SMS ANI and is showing correctly in DID Management going to this extension. SMS is also enabled under my domain.
  22. Looks like that query returns the same results. I'm referencing the https://doc.vodia.com/docs/rest-api-acd-info document and this is the parameter we used to work with: Example: GET https://192.168.1.11/rest/user/45@example/wallboard/73 Returns: {acds: {…}, logged_agents: Array(3), agents: Array(3), current: Array(0), history: Array(3)} JSON object break down: -- This is what gets returned now. https://pbx.com/rest/user/manager@pbx.pbx.com/wallboard/253 http://pbx.com/rest/user/manager@pbx.pbx.com/wallboard/253 { "acds": { "253": { "managers": [ "11", "12", "manager" ], "redirect": { "waiting": 0, "ringing": 0, "anonymous": 0 }, "hangup": { "waiting": 0, "ringing": 0 }, "exit": { "user": 0, "admin": 0, "max-calls": 0, "application": 0, "other": 0 }, "duration": { "sum": { "ivr": 0, "ring": 0, "talk": 0, "hold": 0, "idle": 0 }, "average": { "ivr": 0, "ring": 0, "talk": 0, "hold": 0, "idle": 0 } }, "calls": { "count": 0, "completed": 0 } } }, "agents": [ { "account": "11", "name": "User Agent 1", "dnd": false, "login": true, "jumpin": true, "work": { "begin": 1615525200.0, "end": 1615611600.0, "now": 1615537452.898, "segments": [] }, "calls": 0, "missed": 0, "duration": { "talk": 0, "hold": 0, "idle": 0 }, "average": { "talk": 0, "hold": 0, "idle": 0 } }, { "account": "12", "name": "User Agent 2 .", "dnd": false, "login": true, "jumpin": true, "work": { "begin": 1615525200.0, "end": 1615611600.0, "now": 1615537452.898, "segments": [] }, "calls": 0, "missed": 0, "duration": { "talk": 0, "hold": 0, "idle": 0 }, "average": { "talk": 0, "hold": 0, "idle": 0 } } ], "current": [], "history": [] } --- In this example i have two agents, 11/12, logged into queue 253. The results are different from the example and i'm seeing this new parameter for each agent: "login": true Is this how agents will be tracked as logged in/out going forward? The document isn't that old, recently updated in February. We just want to make sure the method stays the same going forward so we can eliminate the guesswork of future builds.
  23. App version: 3.5.5 Windows MSI file installation Vodia version: 67.0 (win64) My Calls does not show the call. In this example I called two extensions.
×
×
  • Create New...