No RTP Packets, all sorts of issues.

Discussion in '3CX Phone System - General' started by benratty, Jun 7, 2016.

Thread Status:
Not open for further replies.
  1. benratty

    Joined:
    May 23, 2011
    Messages:
    52
    Likes Received:
    0
    I have VOIP Unlimited and Gamma as SIP trunks on my v14 3CX System. Today VOIPUnlimited trunks unregistered because they reported as having a denial of service attack however there where no problems with Gamma.

    When the VOIPUnlimited trunks lost registration the Gamma trunks would no longer function and log shows Internal Server Error and extAddr=0.0.0.0:0 and after speaking at length with Gamma they told me we are not sending the external IP address back so the call does not connect. Which is wasn't. The occasional call would come through but very occasional then fail.

    I did notice that if I took the Put Public IP in SIP VIA Header out and left blank, applied changes then put back in again and applied I could get a few calls through then it would stop again showing extAddr=0.0.0.0:0 and No RTP Packets where received.

    I tried removing the VOIPUnlimited trunks all together which made no difference, restarted services, rebooted system etc... no difference at all. Even tried removing and reading settings like SIP Port, IP addresses etc.. no change.

    Now when the VOIPUnlimited service came back up a few hours later, I had added their trunks back in, they eventually registered again the Gamma trunks also started to function correctly.

    All my calls are set to go out over Gamma trunk only and always have been. Yet I cannot understand how if VOIPUnlimited went down it stopped my system functioning correctly at all.

    I am using 3CX Phone System v14, Split DNS with the Phone System in the exposed in the DMZ and on its own internet connection to which only it is connected. The system used the built in web interface and database, it is on a Dell PowerEdge server with Windows 2012 Standard R2, no firewalls, no other software.

    So am confused now, I never had any problems really with version 12 other than it didn't support Gamma but I used a mix of SIPGate and VOIPUnlimited on two other v12 system with no problems.

    Version 14 seems really buggy.

    It is casuing me a complete nightmare never experienced before and may go back to v12, drop Gamma or mayabe look at alternative to 3CX as what I need it for is mission critical.

    Example problem
    07-Jun-2016 15:02:41.750 [MS105000] C:118.14: No RTP packets were received:remoteAddr=192.168.16.143:11792,extAddr=0.0.0.0:0,localAddr=192.168.16.1:7004
    07-Jun-2016 15:02:41.750 [MS105000] C:118.1: No RTP packets were received:remoteAddr=88.215.55.12:8272,extAddr=0.0.0.0:0,localAddr=*myexternalIP*:9024
    07-Jun-2016 15:02:40.883 Leg L:118.14[Extn] is terminated: Cause: BYE from PBX
    07-Jun-2016 15:02:40.882 Leg L:118.13[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.21:5062
    07-Jun-2016 15:02:40.881 [CM503008]: Call(C:118): Call is terminated
    07-Jun-2016 15:02:40.880 [CM503003]: Call(C:118): Call to <sip:1073@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.21:5062
    07-Jun-2016 15:02:40.838 Leg L:118.1[Line:10000<<*mobilenumber*] is terminated: Cause: BYE from 88.215.55.11:5060
    07-Jun-2016 15:02:40.788 Leg L:118.11[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.20:5062
    07-Jun-2016 15:02:40.787 [CM503003]: Call(C:118): Call to <sip:1050@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.20:5062
    07-Jun-2016 15:02:40.778 Leg L:118.10[Extn] is terminated: Cause: 487 Request Cancelled/INVITE from 192.168.16.13:5060
    07-Jun-2016 15:02:40.777 [CM503003]: Call(C:118): Call to <sip:1030@192.168.16.1:5060> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.16.13:5060
    07-Jun-2016 15:02:40.777 Leg L:118.12[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.178:5062
    07-Jun-2016 15:02:40.776 [CM503003]: Call(C:118): Call to <sip:1077@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.178:5062
    07-Jun-2016 15:02:40.763 Leg L:118.15[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.188:63927
    07-Jun-2016 15:02:40.763 [CM503003]: Call(C:118): Call to <sip:1025@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.188:63927
    07-Jun-2016 15:02:40.657 [CM503007]: Call(C:118): Extn:1078 has joined, contact <sip:1078@192.168.16.143:5062>
    07-Jun-2016 15:02:40.656 [CM503007]: Call(C:118): Line:10000<<*someonesmobilenumber* has joined, contact <sip:*gammatelnum*@88.215.55.11:5060>
    07-Jun-2016 15:02:40.655 L:118.14[Extn] has joined to L:118.1[Line:10000<<*someonesmobilenumber*]
    07-Jun-2016 15:02:40.655 NAT/ALG check:L:118.14[Extn] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    07-Jun-2016 15:02:37.286 Registration attempt for Lc:10001(@VU-Thame03[<sip:*telnum*@sip.voip-unlimited.net:5060>]) is scheduled in 40 sec.
    07-Jun-2016 15:02:34.975 Registration attempt for Lc:10003(@VU-Thame01[<sip:*telnum*@sip.voip-unlimited.net:5060>]) is scheduled in 20 sec.
    07-Jun-2016 15:02:32.503 Leg L:118.2[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
    07-Jun-2016 15:02:32.501 [CM503003]: Call(C:118): Call to <sip:1001@*urltopbx*:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
    07-Jun-2016 15:02:32.467 Leg L:118.7[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.17:5062
    07-Jun-2016 15:02:32.466 [CM503003]: Call(C:118): Call to <sip:1022@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.17:5062
    07-Jun-2016 15:02:32.431 Leg L:118.6[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.140:5062
    07-Jun-2016 15:02:32.429 [CM503003]: Call(C:118): Call to <sip:1009@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.140:5062
    07-Jun-2016 15:02:32.429 Leg L:118.8[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.139:5062
    07-Jun-2016 15:02:32.426 [CM503003]: Call(C:118): Call to <sip:1013@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.139:5062
    07-Jun-2016 15:02:32.426 Leg L:118.9[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.36:5062
    07-Jun-2016 15:02:32.424 [CM503003]: Call(C:118): Call to <sip:1089@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.36:5062
    07-Jun-2016 15:02:32.424 Leg L:118.4[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.29:5062
    07-Jun-2016 15:02:32.423 [CM503003]: Call(C:118): Call to <sip:1004@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.29:5062
    07-Jun-2016 15:02:32.423 Leg L:118.5[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.16:5062
    07-Jun-2016 15:02:32.422 [CM503003]: Call(C:118): Call to <sip:1010@192.168.16.1:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.16.16:5062
    07-Jun-2016 15:02:32.422 Leg L:118.3[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.16.26:5062
     
  2. benratty

    Joined:
    May 23, 2011
    Messages:
    52
    Likes Received:
    0
    Futher to my previous post I did a bit more testing by unregistering VOIPUnlimited by changing their registration address to see what effect this would have. A few minutes later the Gamma trunk stopped functioning again and responding with No RTP Packets sent.

    I registered the VOIPUnlimited trunks again, restarted the services and all trunks started to work again, including Gamma trunks.

    This is a working call log, with a successful call - see bottom part of log in bold as cannot identify what this means either or even if its related.

    07-Jun-2016 21:33:10.005 Leg L:4.2[Ivr] is terminated: Cause: BYE from PBX
    07-Jun-2016 21:33:10.005 [CM503008]: Call(C:4): Call is terminated
    07-Jun-2016 21:33:10.004 Leg L:4.1[Line:10000<<*mobilenumber*] is terminated: Cause: BYE from 88.215.55.11:5060
    07-Jun-2016 21:32:44.788 Currently active calls - 1: [4]
    07-Jun-2016 21:32:12.786 Currently active calls - 1: [4]
    07-Jun-2016 21:31:58.782 [CM503007]: Call(C:4): Ivr:8006 has joined, contact <sip:8006@127.0.0.1:5483>
    07-Jun-2016 21:31:58.781 [CM503007]: Call(C:4): Line:10000<<*mobilenumber* has joined, contact <sip:gamma@88.215.55.11:5060>
    07-Jun-2016 21:31:58.780 L:4.2[Ivr] has joined to L:4.1[Line:10000<<*mobilenumber*]
    07-Jun-2016 21:31:58.780 NAT/ALG check:L:4.2[Ivr] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    07-Jun-2016 21:31:58.630 [CM503025]: Call(C:4): Calling T:Ivr:8006@[Dev:sip:8006@127.0.0.1:5483;rinstance=ab68c4d4d7e7b647] for L:4.1[Line:10000<<*mobilenumber*]
    07-Jun-2016 21:31:58.582 [CM503027]: Call(C:4): From: Line:10000<<*mobilenumber* ("*contactname*" <sip:*mobilenumber*@*serverurl*:5060>) to T:Ivr:8006@[Dev:sip:8006@127.0.0.1:5483;rinstance=ab68c4d4d7e7b647]
    07-Jun-2016 21:31:58.582 [CM503004]: Call(C:4): Route 1: from L:4.1[Line:10000<<*mobilenumber*] to T:Ivr:8006@[Dev:sip:8006@127.0.0.1:5483;rinstance=ab68c4d4d7e7b647]
    07-Jun-2016 21:31:58.582 [CM505003]: Provider:[Gamma Trunk 1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:*serverexternalip*:5060]
    07-Jun-2016 21:31:58.581 [CM503001]: Call(C:4): Incoming call from Line:10000<<*mobilenumber* to <sip:8006@192.168.16.1:5060>
    07-Jun-2016 21:31:58.581 Line limit check: Current # of calls for line Lc:10000(@Gamma Trunk 1[<sip:gamma@88.215.55.11:5060>]) is 1; limit is 64
    07-Jun-2016 21:31:58.581 NAT/ALG check:L:4.1[Line:10000<<*mobilenumber*] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
    Media session IP ('c=' attribute) is not equal to the IP specified in contact header:
    Media session IP:88.215.55.12
    Contact IP:88.215.55.11
    Media session IP ('c=' attribute) is not equal to the SIP packet source(IP:port):
    Media session IP: 88.215.55.12
    Received from: 88.215.55.11
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    Do you use a static public IP, Domain name, or make use of STUN?

    Was the static IP put in when 3CX was first installed?

    Are all of the correct ports forwarded in your router? What make/model router are you using?

    http://www.3cx.com/blog/docs/ports-used/

    Are you using a firewall of any sort?

    Have you successfully run the 3CX firewall Checker?
     
  4. benratty

    Joined:
    May 23, 2011
    Messages:
    52
    Likes Received:
    0
    We have a static public IP address and FQDN for the system in split DNS and it resolves OK. We don't use STUN as been advised by both SIP trunk providers not to use STUN.

    The phone system is exposed so all traffic through the router and firewall go directly to 3CX system.

    Firewall is a checkpoint with Sofaware. Firewall checker responded OK.

    The only one thing I have noticed since is that the server that 3CX is installed on has a second NIC, although not physically connected it was configured. I have disabled this NIC now.
     
  5. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
    Please check if disabling the second NIC solves the problem.

    If it doesn't please open a ticket with our support department write a brief description of your problem and provide us with the support info in verbose so we can investigate further.
     
  6. benratty

    Joined:
    May 23, 2011
    Messages:
    52
    Likes Received:
    0
    How do I open a ticket with support? Our system has been fine all week except around dinner time today there was a brief interruption to the systems internet connection and from then on Gamma is telling us No RTP Packets receieved and that the system is not sending external IP address out. We had not changed anything at all on the system.

    The two other version 12 3cx systems we have where fine and also experienced brief internet connectivity issues but their trunks re-registered and worked without issue. Version 14 seems to be really unstable for us and took hours to get back on again.

    We did disable the second NIC and seemed to resolve some issues like I say it has worked all week without problem up until brief interruption to internet connectivity.
     
  7. benratty

    Joined:
    May 23, 2011
    Messages:
    52
    Likes Received:
    0
    Just further update on these issues.

    I have SIP trunks on my system from two different providers
    VOIPUnlimited - registered trunks by username and password
    Gamma - Authenticated by IP Address

    What I have found after quite a bit of testing is that if for any reason the VOIPUnlimited trunks cannot register about 10 mins later the Gamma trunks stop functioning properly. Not allowing calls in the only occasionally allowing them out.

    The Gamma SIP trunk only starts working again when the VOIPUnlimited trunks register successfully. Then it takes some time before they work fully again.

    The two problems we have so far encountered in both cases VOIPUnlimited Trunks failed to register, on the first occasion the trunk provider had an issue and the second occasion the internet connection was interrupted causing the VOIPUnlimited trunks not to register and it wasn't until they where registered even though internet connectivity was restored that the Gamma SIP trunk started to function again.

    Any thoughts anyone had similar issues with two different providers and different registration methods?
     
  8. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,246
    Likes Received:
    61
Thread Status:
Not open for further replies.