Genesys Cloud - Main

 View Only
Discussion Thread View
Back to discussions
Expand all | Collapse all

Calls rejected - WebRTC

  • 1.  Calls rejected - WebRTC

    Posted 06-29-2020 21:01
    PureCloud is swearing that its on our side but we aren't blocking 5061 and neither is our carrier. This happens when we make calls using WebRTC. Thoughts? 



    17:57:32.519[9f4 tasip.system.proactor][Warning] i3inet::impl::ClientTransaction::on_failure(): failure at step #2:

    ErrorCode:   error.i3inet.transport.tcp.connectionFailure.timeout

    Description: Failed to connect to 107.21.0.113:5061(gjoll.us-east-1.mypurecloud.com:5061) in a timely manner.

    Hostname:    PCE-O39NOUOH5J0

    Function:    i3inet::impl::TcpTransportConnector::on_timeout()

    File(Line):  //core/main_systest/int/src/i3inet/transport_manager.cpp#88(427)

    Parameters:  'peer' => "10 ..


    #SIP/VolP
    #Telephony
    #Unsure/Other

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------


  • 2.  RE: Calls rejected - WebRTC

    GENESYS
    Posted 06-30-2020 09:03
    You might check into NMAP (nmap.org) to test your connection to that gjoll URL.

    For example, I did a test and got the result that port 5061 is open, 0.060s latency:

    C:\Program Files (x86)\nmap-7.80>nmap -Pn gjoll.us-east-1.mypurecloud.com
Starting Nmap 7.80 ( https://nmap.org ) at 2020-06-30 08:54 Eastern Daylight Time
Nmap scan report for gjoll.us-east-1.mypurecloud.com (52.23.42.32)
Host is up (0.060s latency).
Other addresses for gjoll.us-east-1.mypurecloud.com (not scanned): 107.21.0.113 52.20.239.181
Not shown: 999 filtered ports
PORT     STATE SERVICE
5061/tcp open  sip-tls​
    Or for just the IP address you listed:
    C:\Program Files (x86)\nmap-7.80>nmap -Pn 107.21.0.113
Starting Nmap 7.80 ( https://nmap.org ) at 2020-06-30 08:58 Eastern Daylight Time
Nmap scan report for 107.21.0.113
Host is up (0.065s latency).
Not shown: 999 filtered ports
PORT     STATE SERVICE
5061/tcp open  sip-tls​


    ------------------------------
    George Ganahl GCP (Genesys Cloud), ICCE
    Principal Technology Consultant
    Genesys
    ------------------------------

    Original Message


  • 3.  RE: Calls rejected - WebRTC

    Posted 06-30-2020 10:53
    Edited by Bryan De La Cruz 07-03-2020 15:21
    Let me learn to use this tool real fast and I'll update the thread. :)

    Bryan

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 4.  RE: Calls rejected - WebRTC

    Posted 07-03-2020 14:58
    This is what I'm getting. This is my first time using this tool so I may be doing something incorrectly. Thoughts? 

    Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-03 13:56 Central Daylight Time
    NSE: Loaded 151 scripts for scanning.
    NSE: Script Pre-scanning.
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Initiating Ping Scan at 13:56
    Scanning gjoll.us-east-1.mypurecloud.com (52.23.42.32) [4 ports]
    Completed Ping Scan at 13:56, 2.20s elapsed (1 total hosts)
    Nmap scan report for gjoll.us-east-1.mypurecloud.com (52.23.42.32) [host down]
    Other addresses for gjoll.us-east-1.mypurecloud.com (not scanned): 52.20.239.181 107.21.0.113
    NSE: Script Post-scanning.
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Initiating NSE at 13:56
    Completed NSE at 13:56, 0.00s elapsed
    Read data files from: C:\Program Files (x86)\Nmap
    Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
    Nmap done: 1 IP address (0 hosts up) scanned in 3.68 seconds
    Raw packets sent: 8 (304B) | Rcvd: 0 (0B)

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 5.  RE: Calls rejected - WebRTC

    Posted 07-03-2020 15:13
    Edited by Bryan De La Cruz 07-07-2020 12:00
      |   view attached
    I realized that it wasn't working because I hadn't signed in.Ignore screenshot. Here's my test.. It looks like the host is up but 5061 is giving a 403 forbidden. Thoughts? 

    Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-03 14:22 Central Daylight Time
    NSE: Loaded 151 scripts for scanning.
    NSE: Script Pre-scanning.
    Initiating NSE at 14:22
    Completed NSE at 14:22, 0.00s elapsed
    Initiating NSE at 14:22
    Completed NSE at 14:22, 0.00s elapsed
    Initiating NSE at 14:22
    Completed NSE at 14:22, 0.00s elapsed
    Initiating Parallel DNS resolution of 1 host. at 14:22
    Completed Parallel DNS resolution of 1 host. at 14:22, 0.06s elapsed
    Initiating SYN Stealth Scan at 14:22
    Scanning gjoll.us-east-1.mypurecloud.com (52.23.42.32) [1000 ports]
    SYN Stealth Scan Timing: About 29.55% done; ETC: 14:24 (0:01:14 remaining)
    SYN Stealth Scan Timing: About 59.55% done; ETC: 14:24 (0:00:41 remaining)
    Discovered open port 5061/tcp on 52.23.42.32
    Completed SYN Stealth Scan at 14:24, 86.21s elapsed (1000 total ports)
    Initiating Service scan at 14:24
    Scanning 1 service on gjoll.us-east-1.mypurecloud.com (52.23.42.32)
    Completed Service scan at 14:24, 18.04s elapsed (1 service on 1 host)
    Initiating OS detection (try #1) against gjoll.us-east-1.mypurecloud.com (52.23.42.32)
    Retrying OS detection (try #2) against gjoll.us-east-1.mypurecloud.com (52.23.42.32)
    Initiating Traceroute at 14:24
    Completed Traceroute at 14:24, 6.20s elapsed
    Initiating Parallel DNS resolution of 7 hosts. at 14:24
    Completed Parallel DNS resolution of 7 hosts. at 14:24, 11.08s elapsed
    NSE: Script scanning 52.23.42.32.
    Initiating NSE at 14:24
    Completed NSE at 14:24, 0.16s elapsed
    Initiating NSE at 14:24
    Completed NSE at 14:24, 0.36s elapsed
    Initiating NSE at 14:24
    Completed NSE at 14:24, 0.00s elapsed
    Nmap scan report for gjoll.us-east-1.mypurecloud.com (52.23.42.32)
    Host is up (0.060s latency).
    Other addresses for gjoll.us-east-1.mypurecloud.com (not scanned): 107.21.0.113 52.20.239.181
    rDNS record for 52.23.42.32: ec2-52-23-42-32.compute-1.amazonaws.com
    Not shown: 999 filtered ports



    #SIP/VolP
    #Telephony
    #Unsure/Other

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------


  • 6.  RE: Calls rejected - WebRTC

    GENESYS
    Posted 07-03-2020 18:16
    Make sure you run it as  
    nmap -Pn 107.21.0.113​

    or

    nmap -Pn gjoll.us-east-1.mypurecloud.com


    Otherwise it rejects the ping packets.



    ------------------------------
    George Ganahl GCP (Genesys Cloud), ICCE
    Principal Technology Consultant
    Genesys
    ------------------------------

    Original Message


  • 7.  RE: Calls rejected - WebRTC

    Posted 07-07-2020 12:03
    Its telling me the host is down. Is that because my side is blocking or PureCloud's side? Thoughts?

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 8.  RE: Calls rejected - WebRTC

    GENESYS
    Posted 07-08-2020 14:35
    Without seeing the results of the "nmap -Pn ..." scan I couldn't say (and no guarantee I could even with them).

    The gjoll server will never respond to an ICMP ping request (which is what all the other scans you have posted are doing). It is only the -Pn variant which does not do the ICMP ping.

    Since I have no problem getting the response from the gjoll server, I must presume something along the route from your location is being blocked. Wireshark captures might possibly show something...dunno.

    ------------------------------
    George Ganahl GCP (Genesys Cloud), ICCE
    Principal Technology Consultant
    Genesys
    ------------------------------

    Original Message


  • 9.  RE: Calls rejected - WebRTC

    Posted 07-09-2020 13:09
    I pasted the exact command you said to run. -Pn I believe it's along the route too. I haven't testing from the location in question yet because I wanted to simulate the same test from a different PureCloud system to see what it should look like when its successful. Will you please paste what a successful NMAP looks like? 

    Bryan

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 10.  RE: Calls rejected - WebRTC

    GENESYS
    Posted 07-09-2020 13:19

    Ok. I didn't see anything that looks like the results I get, and I didn't see a post that listed that exact command, so I missed it. I am running from the command prompt in Windows 10, so maybe that shows a different result.

    I posted my results earlier, but here they are again:

    C:\Program Files (x86)\nmap-7.80>nmap -Pn gjoll.us-east-1.mypurecloud.com
Starting Nmap 7.80 ( https://nmap.org ) at 2020-06-30 08:54 Eastern Daylight Time
Nmap scan report for gjoll.us-east-1.mypurecloud.com (52.23.42.32)
Host is up (0.060s latency).
Other addresses for gjoll.us-east-1.mypurecloud.com (not scanned): 107.21.0.113 52.20.239.181
Not shown: 999 filtered ports
PORT     STATE SERVICE
5061/tcp open  sip-tls​

    Or for just the IP address you listed:

    C:\Program Files (x86)\nmap-7.80>nmap -Pn 107.21.0.113
Starting Nmap 7.80 ( https://nmap.org ) at 2020-06-30 08:58 Eastern Daylight Time
Nmap scan report for 107.21.0.113
Host is up (0.065s latency).
Not shown: 999 filtered ports
PORT     STATE SERVICE
5061/tcp open  sip-tls​


    ------------------------------
    George Ganahl GCP (Genesys Cloud), ICCE
    Principal Technology Consultant
    Genesys
    ------------------------------

    Original Message


  • 11.  RE: Calls rejected - WebRTC

    Posted 07-09-2020 15:51
    How about this "Nmap -Pn" result George? Was this one done the way you suggested? It appears so since its showing the host is up right? 

    Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-09 12:05 Central Daylight Time
    Nmap scan report for ec2-107-21-0-113.compute-1.amazonaws.com (107.21.0.113)
    Host is up (0.058s latency).
    Not shown: 999 filtered ports
    PORT STATE SERVICE
    5061/tcp open sip-tls

    Nmap done: 1 IP address (1 host up) scanned in 107.42 seconds

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 12.  RE: Calls rejected - WebRTC

    Posted 07-08-2020 12:12
    @Robert Wakefield-Carl​   Will you take a look at this issue with me please? I'm trying to determine why this purecloud host isn't showing up down? If its my side or their side? I've tested from different physical locations to make sure it wasn't the firewall. I've pasted the NMAP logs below. 

    Bryan

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------

    Original Message


  • 13.  RE: Calls rejected - WebRTC

    Posted 03-23-2021 18:07
    @Bryan De La Cruz
    Hi
    Did you found the cause of the issue?​

    ------------------------------
    Gladys Galabay
    High Telecommunications Sociedad de Telecomunicaciones Cia. Ltda.
    ------------------------------

    Original Message


  • 14.  RE: Calls rejected - WebRTC

    Posted 07-06-2020 14:53
    Edited by Bryan De La Cruz 07-06-2020 14:56

    This is what I got back for nmap -T4 -A -v gjoll.us-east-1.mypurecloud.com


    Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-06 13:54 Central Daylight Time
    NSE: Loaded 151 scripts for scanning.
    NSE: Script Pre-scanning.
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Initiating Ping Scan at 13:54
    Scanning gjoll.us-east-1.mypurecloud.com (52.20.239.181) [4 ports]
    Completed Ping Scan at 13:54, 2.21s elapsed (1 total hosts)
    Nmap scan report for gjoll.us-east-1.mypurecloud.com (52.20.239.181) [host down]
    Other addresses for gjoll.us-east-1.mypurecloud.com (not scanned): 107.21.0.113 52.23.42.32
    NSE: Script Post-scanning.
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Initiating NSE at 13:54
    Completed NSE at 13:54, 0.00s elapsed
    Read data files from: C:\Program Files (x86)\Nmap
    Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
    Nmap done: 1 IP address (0 hosts up) scanned in 3.70 seconds
    Raw packets sent: 8 (304B) | Rcvd: 0 (0B)


    And this for nmap -T4 -A -v 107.21.0.113

    Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-06 13:55 Central Daylight Time
    NSE: Loaded 151 scripts for scanning.
    NSE: Script Pre-scanning.
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Initiating Ping Scan at 13:55
    Scanning 107.21.0.113 [4 ports]
    Completed Ping Scan at 13:55, 2.21s elapsed (1 total hosts)
    Nmap scan report for 107.21.0.113 [host down]
    NSE: Script Post-scanning.
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Initiating NSE at 13:55
    Completed NSE at 13:55, 0.00s elapsed
    Read data files from: C:\Program Files (x86)\Nmap
    Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
    Nmap done: 1 IP address (0 hosts up) scanned in 3.70 seconds
    Raw packets sent: 8 (304B) | Rcvd: 0 (0B)

    #SIP/VolP
    #Telephony
    #Unsure/Other

    ------------------------------
    Bryan De La Cruz
    Island Mountain Development Group
    ------------------------------


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources