No RTP packets were received:remoteAddr Cisco 7940

Discussion in '3CX Phone System - General' started by sjm97, Jun 27, 2014.

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

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    hello I have just installed a cisco 7940G ip phone and 3cx but when I call any other extensions I get this error saying [MS105000] C:2.2: No RTP packets were received:remoteAddr=192.168.0.9:40026,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7006. when I call another extension the phone rings but as soon as I pick up it ends so I am at a loss what to do right now any help would be much appreciated. server log below
    Start of log/
    27-Jun-2014 18:42:53.430 [MS105000] C:2.2: No RTP packets were received:remoteAddr=192.168.0.9:40026,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7006
    27-Jun-2014 18:42:53.169 [MS105000] C:2.1: No RTP packets were received:remoteAddr=192.168.0.15:27392,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7004
    27-Jun-2014 18:42:51.759 Leg L:2.2[Extn] is terminated: Cause: BYE from PBX
    27-Jun-2014 18:42:51.758 [CM503008]: Call(C:2): Call is terminated
    27-Jun-2014 18:42:51.756 Leg L:2.1[Extn] is terminated: Cause: BYE from 192.168.0.15:51283
    27-Jun-2014 18:42:51.428 [CM503007]: Call(C:2): Extn:102 has joined, contact <sip:102@192.168.0.9:5077>
    27-Jun-2014 18:42:51.427 [CM503007]: Call(C:2): Extn:100 has joined, contact <sip:100@192.168.0.15:5060>
    27-Jun-2014 18:42:51.424 L:2.2[Extn] has joined to L:2.1[Extn]
    27-Jun-2014 18:42:47.018 [CM503025]: Call(C:2): Calling T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob] for L:2.1[Extn]
    27-Jun-2014 18:42:46.974 [CM503027]: Call(C:2): From: Extn:100 ("Sam " <sip:100@192.168.0.222:5060>) to T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob]
    27-Jun-2014 18:42:46.974 [CM503004]: Call(C:2): Route 1: from L:2.1[Extn] to T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob]
    27-Jun-2014 18:42:46.967 [CM503001]: Call(C:2): Incoming call from Extn:100 to <sip:102@192.168.0.222:5060>
    27-Jun-2014 18:42:43.081 [MS105000] C:1.1: No RTP packets were received:remoteAddr=192.168.0.15:21654,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7000
    27-Jun-2014 18:42:41.744 Leg L:1.2[Ivr] is terminated: Cause: BYE from PBX
    27-Jun-2014 18:42:41.744 [CM503008]: Call(C:1): Call is terminated
    27-Jun-2014 18:42:41.741 Leg L:1.1[Extn] is terminated: Cause: BYE from 192.168.0.15:51278
    27-Jun-2014 18:42:41.280 [CM503007]: Call(C:1): Ivr:800 has joined, contact <sip:800@127.0.0.1:40600>
    27-Jun-2014 18:42:41.275 [CM503007]: Call(C:1): Extn:100 has joined, contact <sip:100@192.168.0.15:5060>
    27-Jun-2014 18:42:41.270 L:1.2[Ivr] has joined to L:1.1[Extn]
    27-Jun-2014 18:42:41.119 [CM503025]: Call(C:1): Calling T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=98876c1b260bcce0] for L:1.1[Extn]
    27-Jun-2014 18:42:41.077 [CM503027]: Call(C:1): From: Extn:100 ("Sam " <sip:100@192.168.0.222:5060>) to T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=98876c1b260bcce0]
    27-Jun-2014 18:42:41.077 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=98876c1b260bcce0]
    27-Jun-2014 18:42:41.075 [CM503001]: Call(C:1): Incoming call from Extn:100 to <sip:800@192.168.0.222:5060>
    27-Jun-2014 18:42:14.212 [CM504001]: Endpoint Ivr:EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600 / EndCall]
    27-Jun-2014 18:42:14.211 [CM504001]: Endpoint Ivr:800: new contact is registered. Contact(s): [sip:800@127.0.0.1:40600 / 800]
    27-Jun-2014 18:42:14.210 [CM504001]: Endpoint Ivr:HOL: new contact is registered. Contact(s): [sip:HOL@127.0.0.1:40600 / HOL]
    27-Jun-2014 18:42:14.186 [CM504001]: Endpoint VMail:666: new contact is registered. Contact(s): [sip:666@127.0.0.1:40600 / 666]
    27-Jun-2014 18:42:10.287 [CM504001]: Endpoint ParkOrb:*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000 / *1]
    27-Jun-2014 18:42:10.287 [CM504001]: Endpoint ParkOrb:*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000 / *0]
    27-Jun-2014 18:42:10.282 [CM504001]: Endpoint ParkOrb:*888: new contact is registered. Contact(s): [sip:*888@127.0.0.1:40000 / *888]
    27-Jun-2014 18:42:10.263 [CM504001]: Endpoint ParkOrb:*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000 / *777]
    27-Jun-2014 18:42:06.078 [CM504004]: Registration succeeded for: Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    27-Jun-2014 18:42:05.680 [CM504003]: Sent registration request for Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    27-Jun-2014 18:42:05.438 IP(s) added:[192.168.0.222]
    27-Jun-2014 18:42:01.967 [CM504008]: Fax Service: Fax.888 registered as sip:888@127.0.0.1:5060 with contact sip:888@127.0.0.1:5100;user=phone
    27-Jun-2014 18:42:00.245 [EC200002]: Media server is connected:
    application:3cx-PC:0/MediaServer
    local:127.0.0.1:5482
    remote:127.0.0.1:49382
    27-Jun-2014 18:41:57.153 [CM504004]: Registration succeeded for: Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    27-Jun-2014 18:41:56.687 [CM504003]: Sent registration request for Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    27-Jun-2014 18:41:56.630 [CM506002]: Resolved SIP external IP:port (90.204.75.250:5060) on Transport 192.168.0.222:5060
    27-Jun-2014 18:41:56.555 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 217.10.68.152:3478 over Transport 192.168.0.222:5060
    27-Jun-2014 18:41:55.380 [CM501006]: Default Local IP address: [192.168.0.222,fe80::c564:40d3:adf9:1e39,::1,fe80::5efe:c0a8:de,fe80::100:7f:fffe]
    27-Jun-2014 18:41:55.372 [CM501002]: Version: 12.0.34969.0
    27-Jun-2014 18:41:55.372 [CM501001]: Start 3CX PhoneSystem Call Manager
    27-Jun-2014 18:41:55.372 [CM501010]: License Info: Load Failed - Error licence Licence: 27 System: 2
    27-Jun-2014 18:41:55.367 Media server is not running
    27-Jun-2014 18:41:55.174 [CM501007]: *** Started Calls Controller thread ***
    /end of log
     
  2. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    Whenver I've experienced thatt issue with an external extenion the way I'd overcome that issue wouldbe to goo to the setting node---> advance---> check allow calls to external from/to exsternal SIP---> also unput your external IP as opposed to your LAN ip make a test call.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    Thanks for replying but all the extensions are internal (3CX phone on ios) and the cisco phone on my desk so i don't know wether that will help but ill give it a go and get back to you
     
  4. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    Sure feel free to give it a try and let me know the results should work with no issues at all.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    well just tried your method but no luck still this is the server log now

    start of log

    28-Jun-2014 14:16:03.236 Leg L:5.4[VMail] is terminated: Cause: BYE from PBX
    28-Jun-2014 14:16:03.235 [CM503008]: Call(C:5): Call is terminated
    28-Jun-2014 14:16:03.232 Leg L:5.1[Extn] is terminated: Cause: BYE from 192.168.0.9:5077
    28-Jun-2014 14:15:58.299 Leg L:5.2[VMail] is terminated: Cause: BYE from 127.0.0.1:40600
    28-Jun-2014 14:15:58.095 [CM503007]: Call(C:5): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:15:58.088 L:5.4[VMail] has joined to L:5.1[Extn]
    28-Jun-2014 14:15:57.946 [CM503025]: Call(C:5): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:5.1[Extn]
    28-Jun-2014 14:15:57.892 [CM503005]: Call(C:5): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:15:57.892 L:5.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NoAnsw]
    28-Jun-2014 14:15:57.891 L:5.1[Extn] failed to reach Extn:100, reason No Answer
    28-Jun-2014 14:15:50.997 Currently active calls - 1: [5]
    28-Jun-2014 14:15:37.863 [CM503025]: Call(C:5): Calling T:Extn:100@[Dev:sip:100@192.168.0.15:5060;transport=udp] for L:5.1[Extn]
    28-Jun-2014 14:15:37.808 [CM503027]: Call(C:5): From: Extn:102 ("102" <sip:102@192.168.0.222:5060>) to T:Extn:100@[Dev:sip:100@192.168.0.15:5060;transport=udp]
    28-Jun-2014 14:15:37.808 [CM503004]: Call(C:5): Route 1: from L:5.1[Extn] to T:Extn:100@[Dev:sip:100@192.168.0.15:5060;transport=udp]
    28-Jun-2014 14:15:33.472 [CM504001]: Endpoint Extn:100: new contact is registered. Contact(s): [sip:100@192.168.0.15:5060 / 100]
    28-Jun-2014 14:15:32.512 [CM503007]: Call(C:5): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:15:32.508 [CM503007]: Call(C:5): Extn:102 has joined, contact <sip:102@192.168.0.9:5077>
    28-Jun-2014 14:15:32.504 L:5.2[VMail] has joined to L:5.1[Extn]
    28-Jun-2014 14:15:32.355 [CM503025]: Call(C:5): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:5.1[Extn]
    28-Jun-2014 14:15:32.305 [CM503005]: Call(C:5): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:15:32.305 L:5.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NotReg]
    28-Jun-2014 14:15:32.304 L:5.1[Extn] failed to reach Extn:100, reason Not Registered
    28-Jun-2014 14:15:32.304 [CM503017]: Call(C:5): Target is not registered: Extn:100
    28-Jun-2014 14:15:32.301 [CM503001]: Call(C:5): Incoming call from Extn:102 to <sip:100@192.168.0.222:5060>
    28-Jun-2014 14:15:17.451 [MS105000] C:4.1: No RTP packets were received:remoteAddr=192.168.0.15:26410,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7016
    28-Jun-2014 14:15:16.514 Leg L:4.2[Ivr] is terminated: Cause: BYE from PBX
    28-Jun-2014 14:15:16.514 [CM503008]: Call(C:4): Call is terminated
    28-Jun-2014 14:15:16.511 Leg L:4.1[Extn] is terminated: Cause: BYE from 192.168.0.15:51631
    28-Jun-2014 14:15:16.059 [CM503007]: Call(C:4): Ivr:800 has joined, contact <sip:800@127.0.0.1:40600>
    28-Jun-2014 14:15:16.057 [CM503007]: Call(C:4): Extn:100 has joined, contact <sip:100@192.168.0.15:5060>
    28-Jun-2014 14:15:16.051 L:4.2[Ivr] has joined to L:4.1[Extn]
    28-Jun-2014 14:15:15.846 [CM503025]: Call(C:4): Calling T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=e696ccc57ad9c779] for L:4.1[Extn]
    28-Jun-2014 14:15:15.754 [CM503027]: Call(C:4): From: Extn:100 ("Sam " <sip:100@192.168.0.222:5060>) to T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=e696ccc57ad9c779]
    28-Jun-2014 14:15:15.754 [CM503004]: Call(C:4): Route 1: from L:4.1[Extn] to T:Ivr:800@[Dev:sip:800@127.0.0.1:40600;rinstance=e696ccc57ad9c779]
    28-Jun-2014 14:15:15.751 [CM503001]: Call(C:4): Incoming call from Extn:100 to <sip:800@192.168.0.222:5060>
    28-Jun-2014 14:14:57.591 Leg L:3.1[Extn] is terminated: Cause: BYE from PBX
    28-Jun-2014 14:14:57.553 [CM503020]: Call(C:3): Normal call termination. Call originator: Extn:100. Reason: Not found
    28-Jun-2014 14:14:57.553 [CM503014]: Call(C:3): No known route from Extn:100 to target: <sip:201@192.168.0.222:5060>
    28-Jun-2014 14:14:57.553 Call(C:3): from Extn:100 to 201 doesn't match any known extension number.
    28-Jun-2014 14:14:57.553 [Flow] Target endpoint for 201 can not be built!
    28-Jun-2014 14:14:57.550 [CM503001]: Call(C:3): Incoming call from Extn:100 to <sip:201@192.168.0.222:5060>
    28-Jun-2014 14:13:31.026 Leg L:2.1[Extn] is terminated: Cause: BYE from PBX
    28-Jun-2014 14:13:31.026 [CM503008]: Call(C:2): Call is terminated
    28-Jun-2014 14:13:31.023 Leg L:2.5[VMail] is terminated: Cause: BYE from 127.0.0.1:40600
    28-Jun-2014 14:13:23.121 Leg L:2.4[VMail] is terminated: Cause: BYE from 127.0.0.1:40600
    28-Jun-2014 14:13:22.916 [CM503007]: Call(C:2): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:13:22.909 L:2.5[VMail] has joined to L:2.1[Extn]
    28-Jun-2014 14:13:22.752 [CM503025]: Call(C:2): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:2.1[Extn]
    28-Jun-2014 14:13:22.699 [CM503005]: Call(C:2): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:13:22.699 L:2.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NotReg]
    28-Jun-2014 14:13:22.699 L:2.1[Extn] failed to reach Extn:100, reason Not Registered
    28-Jun-2014 14:13:22.699 [CM503017]: Call(C:2): Target is not registered: Extn:100
    28-Jun-2014 14:13:20.958 Currently active calls - 1: [2]
    28-Jun-2014 14:13:18.112 Leg L:2.3[VMail] is terminated: Cause: BYE from 127.0.0.1:40600
    28-Jun-2014 14:13:17.909 [CM503007]: Call(C:2): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:13:17.903 L:2.4[VMail] has joined to L:2.1[Extn]
    28-Jun-2014 14:13:17.743 [CM503025]: Call(C:2): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:2.1[Extn]
    28-Jun-2014 14:13:17.689 [CM503005]: Call(C:2): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:13:17.689 L:2.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NotReg]
    28-Jun-2014 14:13:17.689 L:2.1[Extn] failed to reach Extn:100, reason Not Registered
    28-Jun-2014 14:13:17.689 [CM503017]: Call(C:2): Target is not registered: Extn:100
    28-Jun-2014 14:13:11.953 Leg L:2.2[VMail] is terminated: Cause: BYE from 127.0.0.1:40600
    28-Jun-2014 14:13:11.762 [CM503007]: Call(C:2): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:13:11.738 L:2.3[VMail] has joined to L:2.1[Extn]
    28-Jun-2014 14:13:11.584 [CM503025]: Call(C:2): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:2.1[Extn]
    28-Jun-2014 14:13:11.529 [CM503005]: Call(C:2): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:13:11.529 L:2.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NotReg]
    28-Jun-2014 14:13:11.529 L:2.1[Extn] failed to reach Extn:100, reason Not Registered
    28-Jun-2014 14:13:11.529 [CM503017]: Call(C:2): Target is not registered: Extn:100
    28-Jun-2014 14:13:04.835 [CM503007]: Call(C:2): VMail:666 has joined, contact <sip:666@127.0.0.1:40600>
    28-Jun-2014 14:13:04.833 [CM503007]: Call(C:2): Extn:102 has joined, contact <sip:102@192.168.0.9:5077>
    28-Jun-2014 14:13:04.830 L:2.2[VMail] has joined to L:2.1[Extn]
    28-Jun-2014 14:13:04.677 [CM503025]: Call(C:2): Calling T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b] for L:2.1[Extn]
    28-Jun-2014 14:13:04.628 [CM503005]: Call(C:2): Forwarding: T:VMail:666@[Dev:sip:666@127.0.0.1:40600;rinstance=9bf75005c62c572b]
    28-Jun-2014 14:13:04.628 L:2.1[Extn] forwards call from Extn:100 to VMail:666 based on rule Fwd[Available/NotReg]
    28-Jun-2014 14:13:04.627 L:2.1[Extn] failed to reach Extn:100, reason Not Registered
    28-Jun-2014 14:13:04.627 [CM503017]: Call(C:2): Target is not registered: Extn:100
    28-Jun-2014 14:13:04.623 [CM503001]: Call(C:2): Incoming call from Extn:102 to <sip:100@192.168.0.222:5060>
    28-Jun-2014 14:12:58.425 [MS105000] C:1.1: No RTP packets were received:remoteAddr=192.168.0.15:19030,extAddr=0.0.0.0:0,localAddr=192.168.0.222:7000
    28-Jun-2014 14:12:57.706 Leg L:1.2[Extn] is terminated: Cause: BYE from PBX
    28-Jun-2014 14:12:57.706 [CM503008]: Call(C:1): Call is terminated
    28-Jun-2014 14:12:57.703 Leg L:1.1[Extn] is terminated: Cause: BYE from 192.168.0.15:51622
    28-Jun-2014 14:12:57.381 [CM503007]: Call(C:1): Extn:102 has joined, contact <sip:102@192.168.0.9:5077>
    28-Jun-2014 14:12:57.379 [CM503007]: Call(C:1): Extn:100 has joined, contact <sip:100@192.168.0.15:5060>
    28-Jun-2014 14:12:57.374 L:1.2[Extn] has joined to L:1.1[Extn]
    28-Jun-2014 14:12:50.933 Currently active calls - 1: [1]
    28-Jun-2014 14:12:47.720 [CM503025]: Call(C:1): Calling T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob] for L:1.1[Extn]
    28-Jun-2014 14:12:47.713 [CM503027]: Call(C:1): From: Extn:100 ("Sam " <sip:100@192.168.0.222:5060>) to T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob]
    28-Jun-2014 14:12:47.713 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Extn:102@[Dev:sip:102@192.168.0.9:5077;ob]
    28-Jun-2014 14:12:47.683 [CM503001]: Call(C:1): Incoming call from Extn:100 to <sip:102@192.168.0.222:5060>
    28-Jun-2014 14:12:33.387 [CM504001]: Endpoint Extn:102: new contact is registered. Contact(s): [sip:102@192.168.0.9:5077 / 102]
    28-Jun-2014 14:08:45.079 [IPBL] Packet from banned IP/range: ip = 192.168.0.9; Comment: PBX: blocked for too many failed authentications
    28-Jun-2014 14:07:13.741 [CM504001]: Endpoint Ivr:EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600 / EndCall]
    28-Jun-2014 14:07:13.741 [CM504001]: Endpoint Ivr:800: new contact is registered. Contact(s): [sip:800@127.0.0.1:40600 / 800]
    28-Jun-2014 14:07:13.740 [CM504001]: Endpoint Ivr:HOL: new contact is registered. Contact(s): [sip:HOL@127.0.0.1:40600 / HOL]
    28-Jun-2014 14:07:13.698 [CM504001]: Endpoint VMail:666: new contact is registered. Contact(s): [sip:666@127.0.0.1:40600 / 666]
    28-Jun-2014 14:07:02.059 [CM504001]: Endpoint ParkOrb:*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000 / *1]
    28-Jun-2014 14:07:02.059 [CM504001]: Endpoint ParkOrb:*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000 / *0]
    28-Jun-2014 14:07:02.057 [CM504001]: Endpoint ParkOrb:*888: new contact is registered. Contact(s): [sip:*888@127.0.0.1:40000 / *888]
    28-Jun-2014 14:07:02.039 [CM504001]: Endpoint ParkOrb:*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000 / *777]
    28-Jun-2014 14:06:58.898 [CM504004]: Registration succeeded for: Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    28-Jun-2014 14:06:58.573 [CM504003]: Sent registration request for Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    28-Jun-2014 14:06:58.409 IP(s) added:[192.168.0.222]
    28-Jun-2014 14:06:54.028 [EC200002]: Media server is connected:
    application:3cx-PC:0/MediaServer
    local:127.0.0.1:5482
    remote:127.0.0.1:49243
    28-Jun-2014 14:06:50.590 [CM504004]: Registration succeeded for: Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    28-Jun-2014 14:06:50.229 [CM504003]: Sent registration request for Lc:10000(@2111689[<sip:2111689@sipgate.co.uk:5060>])
    28-Jun-2014 14:06:50.177 [CM506002]: Resolved SIP external IP:port (90.204.75.250:5060) on Transport 192.168.0.222:5060
    28-Jun-2014 14:06:50.046 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 198.50.247.220:3478 over Transport 192.168.0.222:5060
    28-Jun-2014 14:06:48.567 [CM501006]: Default Local IP address: [192.168.0.222,fe80::c564:40d3:adf9:1e39,::1,fe80::5efe:c0a8:de,2001:0:5ef5:79fb:28b0:1f69:3f57:ff21,fe80::28b0:1f69:3f57:ff21]
    28-Jun-2014 14:06:48.559 [CM501002]: Version: 12.0.34969.0
    28-Jun-2014 14:06:48.559 [CM501001]: Start 3CX PhoneSystem Call Manager
    28-Jun-2014 14:06:48.558 [CM501010]: License Info: Load Failed - Error licence Licence: 27 System: 2
    28-Jun-2014 14:06:48.510 Media server is not running
    28-Jun-2014 14:06:48.313 [CM501007]: *** Started Calls Controller thread ***
    end of log

    Any ideas now ? and thanks for your help
     
  6. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    aswell the cisco phone no longer rings when dialled now
     
  7. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    You may have several things going on (second log) -

    The first issue is that the extension you were trying to reach initially (102) was blocked for too many failed authorizations. It looks like you fixed this as the extension registered some 4 minutes later. Then it looks like the two extensions did connect, but apparently were not able to negotiate and disconnected. Then extension 100 went off-line and the registration was gone subsequently putting extension 102 into the vmail of 100. Then, almost a minute and a half later, there was an attempt to connect to extension 201 which does not exist. Some 18 seconds after that call, extension 100 called into the IVR. Finally another attempt was made to call ext 100 from ext 102, but again ext 100 was not registered, so back to vmail.

    Disable the SIP settings for the moment as this allows for direct SIP calling. It is not needed for internal calls and can always be turned back on later if needed.

    You did not mention how the phones were provisioned. Did you do these manually or by using the 3CX provided template? You can follow the guides in the following link to ensure the the phones are SIP capable and provisioned correctly.
    http://www.3cx.com/blog/docs/cisco-7940-ip-phone/

    Once the above is assured, then you might try turning off the firewall on your system should one be in existence and active. The firewall checker does not check for internal ports, only those that will be used externally. It may be that your installation of the system failed to open these. You can always go back and edit if need be and turn it back on.

    You also apparently were sent to vmail and to an IVR, both of which presumably sent out messages. Did you hear these?

    Another thing that you can do is to check the box for each extension for the PBX to provide audio. I don't normally do this as it forces the PBX to do some additional work that for an internal call it should not have to as the phones should be able to communicate to one another directly. Nevertheless for testing purposes, you can try this.

    try and stay to testing one aspect and with one scenario. There seemed to be a problem with the phones staying registered and this is the more severe issue. If they remain registered, then the audio (RTP) issue can be addressed more solidly without having to worry about other things going on.
     
  8. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    just tried doing what you suggested I managed to get the cisco connected again but wont ring from other phones but I can ring other phones but still wont connect I also tried calling 666 to access the vmail but still no luck. I used the phone provisioning feature in 3CX but still no luck still getting the no RTP packet were received
     
  9. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    ok....

    what version of 3cx are you running? i noticed that the license load failed. what os and system?

    are the cisco phones solidly registered?
    are all the 3cx sevices running when making the calls and do the system extensions show registered?
    is the windows or other firewall on the system off?
    is the box for pbx provides audio checked?
    assuming you do have the cisco compatible sip firmware loaded, you might consider resetting the phone and attempt to re-provision using the templates.
    turn on verbose mode on the logs.

    you can also do the echo test *777
     
  10. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    3cx version is 12 free and the os is windows 7 pro x86 (32 bit)
    (are the cisco phones solidly registered?) Im not sure what you mean I take it that 3cx lists them as registered if so yes
    all of the services in the service status are running
    system extensions are listed as registered
    all firewalls are disabled currently (troubleshooting measure)
    yes that option is checked for the pbx to provide audio
    I converted the phone from sccp to sip using the 3cx tutorial and provisioned it though the extension menu.

    the *777 test gives the same error

    I should also note this only started to happen after a power surge
     
  11. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    To be clear, your statement about the power surge........does this mean that all was well and functioning previously? If so, then the implication is that the original settings were fine in both the phone and the system and should not have changed. Not knowing what the surge may have done, but assuming it is the cause, seems to point more so to a hardware issue or corruption of firmware or software. I assume that you have re-booted the system upon which 3CX resides, if not, then:

    1. Re-boot the system, test again; if not successful
    2. If possible, download, install and configure the 3CX softphone for a new extension. If this works, then there should be no reason that the Cisco should not; unless the surge affected it as well
    3. Make a backup of the 3CX system using the embedded tool and see that it passes the success test, if not successful, then be prepared to manually setup
    4. Delete the current installation and re-install. If the backup was successful, then restore or rebuild manually (your choice depending upon the confidence you have in the backup); test again using both the Softphone and the Cisco.
    5. If the softphone works and the Cisco does not; you may need to do a factory reset or similar and start over with its provisioning.
     
  12. intellegens

    Joined:
    Jun 19, 2013
    Messages:
    18
    Likes Received:
    0
    Have you had a chance to run the firewall checker as recommended earlier? Do all tests pass?
    Thanks
     
  13. sjm97

    Joined:
    Jun 27, 2014
    Messages:
    7
    Likes Received:
    0
    yes it was working with a hiccup now and then and the firewall test passes. regarding your idea about the 3cx softphone that is what all other extensions are using there is only one cisco phone. something strange about the surge both the PoE adapter (cisco AIR-PWRINJ3) and the power supply for it (Cisco AA25480L) both are working fine as I check them with one of my spare AIRONET access points. when the phone powers up now it just reads Ethernet disconnected but on the second Ethernet port (pc) it connects and is recognised by the network and even grabs the logo from the server but port one seems to be dead so im thinking that the phone may be damaged and the phone was working but using cisco's CCM
     
  14. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    yes...seems like a phone issue. I would factory reset and try. if no success.....then time for a new phone.
     
  15. pratap.gouda

    Joined:
    May 13, 2015
    Messages:
    4
    Likes Received:
    0
    hI lneblett,

    I have same issue and i tested with 3 type IP phones. Polycom 501, Cisco 303 and Grandstrem GXP 1405 .. still the same error.

    I configured two ip phone in different location and able to connect to my 3cx sever and register with ext number. even i am able to dial the number and and external ext are ringing but no audio from both the side.

    Please help me.


    [CM503003]: Call(C:49732): Call to <sip:2000@10.20.1.41:5060> has failed; Cause: 408 Request Timeout/INVITE from local
    Leg L:49732.2[Extn] is terminated: Cause: 408 Request Timeout/INVITE from local
    [MS105000] C:49729.1: No RTP packets were received:remoteAddr=xxxxxxx:2230,extAddr=0.0.0.0:0,localAddr=XXXXXXX:9074

    thanks
    PKG
     
  16. Kevin Evans

    Joined:
    Feb 7, 2017
    Messages:
    1
    Likes Received:
    0
    We had a similar issue. Internal phones were not working. [MS105000] C:49729.1: No RTP packets were received:remoteAddr=xxxxxxx:51070,extAddr=0.0.0.0:0,localAddr=XXXXXXX:7080

    Our issue was that we had two IP addresses assigned to the Windows server. We took the second one out and all the phones started working.
    3CX Phone System Standard Edition version 14
     
Thread Status:
Not open for further replies.