Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Extensions work Busy signal for external incoming and outgoing

Discussion in '3CX Phone System - General' started by cdubb79, Nov 7, 2015.

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

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Need help diagnosing this log file. running 2 patton 4114 and 4 gxw4224. I have a Cisco RV320 and i've opened up every port I can think the phone system is using. Any help would be appreciated.

    Leg L:25.1[Extn] is terminated: Cause: BYE from PBX
    07-Nov-2015 13:01:27.229 [CM503020]: Call(C:25): Normal call termination. Call originator: Extn:105. Reason: Not available
    07-Nov-2015 13:01:27.229 L:25.1[Extn] failed to reach Out#:>>Rule{Rule for FXO/1/4}>>96789399229, reason Not Registered
    07-Nov-2015 13:01:27.228 [CM503017]: Call(C:25): Target is not registered: Out#:>>Rule{Rule for FXO/1/4}>>96789399229
    07-Nov-2015 13:01:27.228 Call(C:25): Call from Extn:105 to 96789399229 matches outbound rule 'Rule for FXO/1/4'
    07-Nov-2015 13:01:27.227 [CM503001]: Call(C:25): Incoming call from Extn:105 to <sip:96789399229@192.168.18.201:5060>

    3CX show trunks are registred and idle. The Pattons are FXO and phone lines are working if I plug a phone directly up to them.

    Thanks,
    Chris
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    It would appear that 3CX disagrees that the trunks are registered. Perhaps changing the logs to verbose will provide some additional information.
     
  3. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Here is some Verbose for ya... Thanks again.

    10-Nov-2015 11:20:43.167 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 198.50.247.220:3478 over Transport 192.168.18.201:5060
    10-Nov-2015 11:16:14.642 Leg L:6.1[Extn] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:16:14.601 [CM503020]: Call(C:6): Normal call termination. Call originator: Extn:211. Reason: Not available
    10-Nov-2015 11:16:14.601 L:6.1[Extn] failed to reach Out#:>>Rule{Rule for FXO/1/4}>>96783005054, reason Not Registered
    10-Nov-2015 11:16:14.599 [CM503017]: Call(C:6): Target is not registered: Out#:>>Rule{Rule for FXO/1/4}>>96783005054
    10-Nov-2015 11:16:14.599 Call(C:6): Call from Extn:211 to 96783005054 matches outbound rule 'Rule for FXO/1/4'
    10-Nov-2015 11:16:14.598 [CM503001]: Call(C:6): Incoming call from Extn:211 to <sip:96783005054@192.168.18.201:5060>
    10-Nov-2015 11:16:14.596 NAT/ALG check:L:6.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:15:58.441 Leg L:5.1[Extn] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:15:58.400 [CM503020]: Call(C:5): Normal call termination. Call originator: Extn:211. Reason: Not available
    10-Nov-2015 11:15:58.400 L:5.1[Extn] failed to reach Out#:>>Rule{Rule for FXO/1/4}>>96783005054, reason Not Registered
    10-Nov-2015 11:15:58.399 [CM503017]: Call(C:5): Target is not registered: Out#:>>Rule{Rule for FXO/1/4}>>96783005054
    10-Nov-2015 11:15:58.399 Call(C:5): Call from Extn:211 to 96783005054 matches outbound rule 'Rule for FXO/1/4'
    10-Nov-2015 11:15:58.397 [CM503001]: Call(C:5): Incoming call from Extn:211 to <sip:96783005054@192.168.18.201:5060>
    10-Nov-2015 11:15:58.395 NAT/ALG check:L:5.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:14:52.670 Leg L:4.1[Extn] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:14:52.613 [CM503020]: Call(C:4): Normal call termination. Call originator: Extn:207. Reason: Not available
    10-Nov-2015 11:14:52.613 L:4.1[Extn] failed to reach Out#:>>Rule{Rule for FXO/1/4}>>96783005054, reason Not Registered
    10-Nov-2015 11:14:52.599 [CM503017]: Call(C:4): Target is not registered: Out#:>>Rule{Rule for FXO/1/4}>>96783005054
    10-Nov-2015 11:14:52.599 Call(C:4): Call from Extn:207 to 96783005054 matches outbound rule 'Rule for FXO/1/4'
    10-Nov-2015 11:14:52.598 [CM503001]: Call(C:4): Incoming call from Extn:207 to <sip:96783005054@192.168.18.201:5060>
    10-Nov-2015 11:14:52.573 NAT/ALG check:L:4.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:14:35.390 Leg L:3.1[Extn] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:14:35.349 [CM503020]: Call(C:3): Normal call termination. Call originator: Extn:207. Reason: Not available
    10-Nov-2015 11:14:35.349 L:3.1[Extn] failed to reach Out#:>>Rule{Rule for FXO/1/4}>>96783005054, reason Not Registered
    10-Nov-2015 11:14:35.347 [CM503017]: Call(C:3): Target is not registered: Out#:>>Rule{Rule for FXO/1/4}>>96783005054
    10-Nov-2015 11:14:35.347 Call(C:3): Call from Extn:207 to 96783005054 matches outbound rule 'Rule for FXO/1/4'
    10-Nov-2015 11:14:35.345 [CM503001]: Call(C:3): Incoming call from Extn:207 to <sip:96783005054@192.168.18.201:5060>
    10-Nov-2015 11:14:35.344 NAT/ALG check:L:3.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:14:22.908 Leg L:2.2[Line:10000>>678] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:14:22.908 [CM503008]: Call(C:2): Call is terminated
    10-Nov-2015 11:14:22.906 Leg L:2.1[Extn] is terminated: Cause: BYE from 192.168.18.207:5080
    10-Nov-2015 11:14:19.138 [CM503007]: Call(C:2): Line:10000>>678 has joined, contact <sip:10000@192.168.18.208:5060>
    10-Nov-2015 11:14:19.138 [CM503007]: Call(C:2): Extn:207 has joined, contact <sip:207@192.168.18.207:5080>
    10-Nov-2015 11:14:19.136 L:2.2[Line:10000>>678] has joined to L:2.1[Extn]
    10-Nov-2015 11:14:19.135 NAT/ALG check:L:2.2[Line:10000>>678] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:14:19.135 [CM505002]: Gateway:[FXO 1-4] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA0B7746 R6.3 2013-05-01 H323 SIP FXS FXO M5T SIP Stack/4.1.12.18] PBX contact: [sip:10000@192.168.18.201:5060]
    10-Nov-2015 11:14:16.574 [CM503025]: Call(C:2): Calling T:Line:10000>>678@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063] for L:2.1[Extn]
    10-Nov-2015 11:14:16.544 [CM503027]: Call(C:2): From: Extn:207 (<sip:207@192.168.18.201:5060>) to T:Line:10000>>678@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063]
    10-Nov-2015 11:14:16.544 [CM503004]: Call(C:2): Route 1: from L:2.1[Extn] to T:Line:10000>>678@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063]
    10-Nov-2015 11:14:16.544 Line limit check: Current # of calls for line Lc:10003(@FXO 1-4[<sip:10003@192.168.18.208:5063>]) is 0; limit is 1
    10-Nov-2015 11:14:16.544 Line limit check: Current # of calls for line Lc:10002(@FXO 1-4[<sip:10002@192.168.18.208:5062>]) is 0; limit is 1
    10-Nov-2015 11:14:16.544 Line limit check: Current # of calls for line Lc:10001(@FXO 1-4[<sip:10001@192.168.18.208:5061>]) is 0; limit is 1
    10-Nov-2015 11:14:16.544 Line limit check: Current # of calls for line Lc:10000(@FXO 1-4[<sip:10000@192.168.18.208:5060>]) is 0; limit is 1
    10-Nov-2015 11:14:16.543 Call(C:2): Call from Extn:207 to 9678 matches outbound rule 'Rule for FXO 1-4'
    10-Nov-2015 11:14:16.474 [CM503001]: Call(C:2): Incoming call from Extn:207 to <sip:9678@192.168.18.201:5060>
    10-Nov-2015 11:14:16.472 NAT/ALG check:L:2.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:14:04.966 Leg L:1.2[Line:10000>>] is terminated: Cause: BYE from PBX
    10-Nov-2015 11:14:04.965 [CM503008]: Call(C:1): Call is terminated
    10-Nov-2015 11:14:04.940 Leg L:1.1[Extn] is terminated: Cause: BYE from 192.168.18.207:5080
    10-Nov-2015 11:13:54.802 [CM503007]: Call(C:1): Line:10000>> has joined, contact <sip:10000@192.168.18.208:5060>
    10-Nov-2015 11:13:54.801 [CM503007]: Call(C:1): Extn:207 has joined, contact <sip:207@192.168.18.207:5080>
    10-Nov-2015 11:13:54.670 L:1.2[Line:10000>>] has joined to L:1.1[Extn]
    10-Nov-2015 11:13:54.670 NAT/ALG check:L:1.2[Line:10000>>] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:13:54.670 [CM505002]: Gateway:[FXO 1-4] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA0B7746 R6.3 2013-05-01 H323 SIP FXS FXO M5T SIP Stack/4.1.12.18] PBX contact: [sip:10000@192.168.18.201:5060]
    10-Nov-2015 11:13:52.068 [CM503025]: Call(C:1): Calling T:Line:10000>>@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063] for L:1.1[Extn]
    10-Nov-2015 11:13:51.898 [CM503027]: Call(C:1): From: Extn:207 (<sip:207@192.168.18.201:5060>) to T:Line:10000>>@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063]
    10-Nov-2015 11:13:51.898 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Line:10000>>@[Dev:sip:10000@192.168.18.208:5060,Dev:sip:10001@192.168.18.208:5061,Dev:sip:10002@192.168.18.208:5062,Dev:sip:10003@192.168.18.208:5063]
    10-Nov-2015 11:13:51.856 Line limit check: Current # of calls for line Lc:10003(@FXO 1-4[<sip:10003@192.168.18.208:5063>]) is 0; limit is 1
    10-Nov-2015 11:13:51.856 Line limit check: Current # of calls for line Lc:10002(@FXO 1-4[<sip:10002@192.168.18.208:5062>]) is 0; limit is 1
    10-Nov-2015 11:13:51.856 Line limit check: Current # of calls for line Lc:10001(@FXO 1-4[<sip:10001@192.168.18.208:5061>]) is 0; limit is 1
    10-Nov-2015 11:13:51.856 Line limit check: Current # of calls for line Lc:10000(@FXO 1-4[<sip:10000@192.168.18.208:5060>]) is 0; limit is 1
    10-Nov-2015 11:13:51.713 Call(C:1): Call from Extn:207 to 9 matches outbound rule 'Rule for FXO 1-4'
    10-Nov-2015 11:13:51.406 [CM503001]: Call(C:1): Incoming call from Extn:207 to <sip:9@192.168.18.201:5060>
    10-Nov-2015 11:13:51.194 NAT/ALG check:L:1.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
    10-Nov-2015 11:00:42.969 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 198.50.247.220:3478 over Transport 192.168.18.201:5060
    10-Nov-2015 10:55:41.764 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 212.83.188.161 because it is on blocked UAs list
    10-Nov-2015 10:49:19.805 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 23.239.69.233 because it is on blocked UAs list
    10-Nov-2015 10:40:42.806 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 198.50.247.220:3478 over Transport 192.168.18.201:5060
    10-Nov-2015 10:39:06.934 [CM504001]: Endpoint Extn:130: new contact is registered. Contact(s): [sip:130@192.168.18.207:5062 / 130]
    10-Nov-2015 10:39:05.710 [CM504001]: Endpoint Extn:129: new contact is registered. Contact(s): [sip:129@192.168.18.207:5060 / 129]
    10-Nov-2015 10:39:02.482 [CM504001]: Endpoint Extn:335: new contact is registered. Contact(s): [sip:335@192.168.18.210:5060 / 335]
    10-Nov-2015 10:38:50.390 [CM504001]: Endpoint Extn:334: new contact is registered. Contact(s): [sip:334@192.168.18.206:5106 / 334]
    10-Nov-2015 10:38:50.235 [CM504001]: Endpoint Extn:333: new contact is registered. Contact(s): [sip:333@192.168.18.206:5104 / 333]
    10-Nov-2015 10:38:49.005 [CM504001]: Endpoint Extn:332: new contact is registered. Contact(s): [sip:332@192.168.18.206:5102 / 332]
    10-Nov-2015 10:38:48.783 [CM504001]: Endpoint Extn:331: new contact is registered. Contact(s): [sip:331@192.168.18.206:5100 / 331]
    10-Nov-2015 10:38:48.563 [CM504001]: Endpoint Extn:330: new contact is registered. Contact(s): [sip:330@192.168.18.206:5098 / 330]
    10-Nov-2015 10:38:48.412 [CM504001]: Endpoint Extn:329: new contact is registered. Contact(s): [sip:329@192.168.18.206:5096 / 329]
    10-Nov-2015 10:38:48.191 [CM504001]: Endpoint Extn:328: new contact is registered. Contact(s): [sip:328@192.168.18.206:5094 / 328]
    10-Nov-2015 10:38:48.170 [CM504001]: Endpoint Extn:108: new contact is registered. Contact(s): [sip:108@192.168.18.204:5068 / 108]
    10-Nov-2015 10:38:48.164 [CM504001]: Endpoint Extn:327: new contact is registered. Contact(s): [sip:327@192.168.18.206:5092 / 327]
    10-Nov-2015 10:38:48.059 [CM504001]: Endpoint Extn:107: new contact is registered. Contact(s): [sip:107@192.168.18.204:5066 / 107]
    10-Nov-2015 10:38:47.031 [CM504001]: Endpoint Extn:326: new contact is registered. Contact(s): [sip:326@192.168.18.206:5090 / 326]
    10-Nov-2015 10:38:46.811 [CM504001]: Endpoint Extn:325: new contact is registered. Contact(s): [sip:325@192.168.18.206:5088 / 325]
    10-Nov-2015 10:38:46.591 [CM504001]: Endpoint Extn:323: new contact is registered. Contact(s): [sip:323@192.168.18.206:5084 / 323]
    10-Nov-2015 10:38:46.373 [CM504001]: Endpoint Extn:312: new contact is registered. Contact(s): [sip:312@192.168.18.206:5064 / 312]
    10-Nov-2015 10:38:46.154 [CM504001]: Endpoint Extn:311: new contact is registered. Contact(s): [sip:311@192.168.18.206:5062 / 311]
    10-Nov-2015 10:38:45.819 [CM504001]: Endpoint Extn:128: new contact is registered. Contact(s): [sip:128@192.168.18.204:5106 / 128]
    10-Nov-2015 10:38:45.702 [CM504001]: Endpoint Extn:127: new contact is registered. Contact(s): [sip:127@192.168.18.204:5104 / 127]
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    OK, you have 3 call, toe of which should not go through as they are not complete number, yet, they do pass through to the Gateway. The third call, while appearing to be a valid number (9+10 digits), doesn't get passed on. This would seem to indicate that you have to review how you have constructed the outbound rule(s). A single digit (9), or an incomplete number (9678), should be rejected. This is usually accomplished by specifying the number of digits that make up a valid digit string. If you continue to have problems, post the outbound rule(s) that you are using.


     
  5. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    The mistakes while dialing are evident. I don't have any inbound rules set and I get a straight busy signal. Outbound rules are below. It goes to a busy signal as well. The rules look correct if i'm not mistaken. Right? To me it sounds like the Patton is leaving the phone line off the hook. I've attached what the outbound rules look like.
     

    Attached Files:

  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    I'm not certain what the dial plan is, where you are located, but I assume that you are using a 9 as an outbound prefix, but wish to strip that before sending the digits to the gateway. Since you have 911 as an emergency number, i have to assume you are in North America
    To do some testing, I would construct a rule that is a bit more specific. This can be "tweaked" later on as required to accommodate all number variations.

    If you wish to dial an outside number consisting of 6783005054 using a prefix of 9. Then make a rule where the number starts with 9, is 11 digits long, and strip 1 digit (the 9). Put this after the 911 rule. Rules are read top to bottom.

    If you want to be more specific, restricting a rule to only a local area code, the make the rule consist of the prefix 9678.

    Have a read through this...

    http://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/

    I'm not certain why you cannot receive calls, there may very well be other factors at play here.
     
  7. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Well Outbound rules fixed it. I set a couple inbound rules, but still a busy signal. This may be a stupid question, but in the 3CX console does a VoIP Provider have to listed there? We are using Winstream. I only ask, because it wasn't there initially. I'm simply replacing equipment, but most of the setup is here.

    I also ran a test. May not mean anything, but I called my external phone number from my internal softphone and it rang. Im thinking the disconnect is either with the provider or the Cisco RV320 firewall. FYI. I passed the firewall test in the console.
    Can I get any logs from the Patton?

    13-Nov-2015 03:23:07.552 Leg L:21.3[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.18.102:5062
    13-Nov-2015 03:23:07.552 [CM503003]: Call(C:21): Call to <sip:400@192.168.18.201:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.18.102:5062
    13-Nov-2015 03:23:07.434 [CM503008]: Call(C:21): Call is terminated
    13-Nov-2015 03:23:07.432 Leg L:21.1[Line:10004<<6787050568] is terminated: Cause: CANCEL from 192.168.18.208:5060
    13-Nov-2015 03:23:05.863 Leg L:21.2[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.18.100:5062
    13-Nov-2015 03:23:05.862 [CM503003]: Call(C:21): Call to <sip:100@192.168.18.201:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.18.100:5062
    13-Nov-2015 03:23:05.745 [CM503025]: Call(C:21): Calling T:HuntGrp:800@[Dev:sip:400@192.168.18.102:5062] for L:21.1[Line:10004<<6787050568]
    13-Nov-2015 03:23:03.119 Leg L:20.2[Line:10003>>6787050568] is terminated: Cause: BYE from PBX
    13-Nov-2015 03:23:03.119 [CM503008]: Call(C:20): Call is terminated
    13-Nov-2015 03:23:03.116 Leg L:20.1[Extn] is terminated: Cause: BYE from 192.168.18.201:53170
    13-Nov-2015 03:22:45.737 [CM503025]: Call(C:21): Calling T:HuntGrp:800@[Dev:sip:100@192.168.18.100:5062] for L:21.1[Line:10004<<6787050568]
    13-Nov-2015 03:22:45.634 [CM503027]: Call(C:21): From: Line:10004<<6787050568 (<sip:6787050568@192.168.18.201:5060>) to T:HuntGrp:800@[Dev:sip:400@192.168.18.102:5062]
    13-Nov-2015 03:22:45.634 [CM503004]: Call(C:21): Route 2: from L:21.1[Line:10004<<6787050568] to T:HuntGrp:800@[Dev:sip:400@192.168.18.102:5062]
    13-Nov-2015 03:22:45.607 [CM503027]: Call(C:21): From: Line:10004<<6787050568 (<sip:6787050568@192.168.18.201:5060>) to T:HuntGrp:800@[Dev:sip:100@192.168.18.100:5062]
    13-Nov-2015 03:22:45.606 [CM503004]: Call(C:21): Route 1: from L:21.1[Line:10004<<6787050568] to T:HuntGrp:800@[Dev:sip:100@192.168.18.100:5062]
    13-Nov-2015 03:22:45.400 [CM505002]: Gateway:[Patton 4114_8] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA0B7746 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10] PBX contact: [sip:10004@192.168.18.201:5060]
    13-Nov-2015 03:22:45.399 [CM503001]: Call(C:21): Incoming call from Line:10004<<6787050568 to <sip:800@192.168.18.201:5060>
    13-Nov-2015 03:22:45.398 Line limit check: Current # of calls for line Lc:10004(@Patton 4114_8[<sip:10004@192.168.18.208:5060>]) is 1; limit is 1
    13-Nov-2015 03:22:45.360 NAT/ALG check:L:21.1[Line:10004<<6787050568] REQUEST 'INVITE' - basic check passed. No information for extended checks
    13-Nov-2015 03:22:45.263 [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to DN:800
    13-Nov-2015 03:22:42.391 [CM503007]: Call(C:20): Line:10003>>6787050568 has joined, contact <sip:10003@192.168.18.209:5063>
    13-Nov-2015 03:22:42.390 [CM503007]: Call(C:20): Extn:499 has joined, contact <sip:499@192.168.18.201:53170>
    13-Nov-2015 03:22:42.388 L:20.2[Line:10003>>6787050568] has joined to L:20.1[Extn]
    13-Nov-2015 03:22:42.388 NAT/ALG check:L:20.2[Line:10003>>6787050568] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    13-Nov-2015 03:22:42.388 [CM505002]: Gateway:[Patton 4114] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10] PBX contact: [sip:10003@192.168.18.201:5060]
    13-Nov-2015 03:22:38.172 Currently active calls - 1: [20]
    13-Nov-2015 03:22:37.839 [CM503025]: Call(C:20): Calling T:Line:10003>>6787050568@[Dev:sip:10003@192.168.18.209:5063,Dev:sip:10002@192.168.18.209:5062,Dev:sip:10001@192.168.18.209:5061,Dev:sip:10000@192.168.18.209:5060] for L:20.1[Extn]
    13-Nov-2015 03:22:37.791 [CM503027]: Call(C:20): From: Extn:499 ("Chris Ward" <sip:499@192.168.18.201:5060>) to T:Line:10003>>6787050568@[Dev:sip:10003@192.168.18.209:5063,Dev:sip:10002@192.168.18.209:5062,Dev:sip:10001@192.168.18.209:5061,Dev:sip:10000@192.168.18.209:5060]
    13-Nov-2015 03:22:37.791 [CM503004]: Call(C:20): Route 1: from L:20.1[Extn] to T:Line:10003>>6787050568@[Dev:sip:10003@192.168.18.209:5063,Dev:sip:10002@192.168.18.209:5062,Dev:sip:10001@192.168.18.209:5061,Dev:sip:10000@192.168.18.209:5060]
    13-Nov-2015 03:22:37.791 Line limit check: Current # of calls for line Lc:10000(@Patton 4114[<sip:10000@192.168.18.209:5060>]) is 0; limit is 1
    13-Nov-2015 03:22:37.791 Line limit check: Current # of calls for line Lc:10001(@Patton 4114[<sip:10001@192.168.18.209:5061>]) is 0; limit is 1
    13-Nov-2015 03:22:37.791 Line limit check: Current # of calls for line Lc:10002(@Patton 4114[<sip:10002@192.168.18.209:5062>]) is 0; limit is 1
    13-Nov-2015 03:22:37.791 Line limit check: Current # of calls for line Lc:10003(@Patton 4114[<sip:10003@192.168.18.209:5063>]) is 0; limit is 1
    13-Nov-2015 03:22:37.791 Call(C:20): Call from Extn:499 to 96787050568 matches outbound rule 'Rule for FXO/1/4'
    13-Nov-2015 03:22:37.789 [CM503001]: Call(C:20): Incoming call from Extn:499 to <sip:96787050568@192.168.18.201:5060>
    13-Nov-2015 03:22:37.788 NAT/ALG check:L:20.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
     
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    Most providers will work even if they are not listed, but, that's not a guarantee, a few have some very specific and not standard requirements. There is a generic profile that can be used for non-supported providers. If your providers shows as registered, and you now able to place outgoing calls, the trunk settings are probably correct.

    How are you dealing with incoming calls? Where are you sending them? What does the server log show for one of the failed calls? Have you tried a very simple inbound set-up, where you send all calls to a ring group, or one extension, as a test?
     
  9. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Well outgoing calls works without a provider setup. I'm not getting anything in the log file for inbound calls. It's like they don't exist. Calling internal extensions work fine. But I get nothing from external callers but a busy signal and no log data. Im set to ring to a group 800. All extensions are registered. Even the System extensions. I can call the group from the internal softphone as well.
     
  10. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Here is a debug log from one of the Pattons. Just registering.

    11:14:59 SIP_TR> [STACK] < 453 Stack: from 192.168.18.201
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.18.209:5063;branch=z9hG4bK62450499d21b674a5
    Proxy-Authenticate: Digest nonce="414d535c0c56446235:9b8c0dc610e9da95df597b9464628680",algorithm=MD5,realm="3CXPhoneSystem"
    To: <sip:10003@192.168.18.201>;tag=c153ad6e
    From: <sip:10003@192.168.18.201>;tag=7099fb862c
    Call-ID: b8aedf5d1bb1c1ed
    CSeq: 16310 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] > 657 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5063;branch=z9hG4bKa01b6a19714604d89
    Proxy-Authorization: Digest username="10003",realm="3CXPhoneSystem",nonce="414d535c0c56446235:9b8c0dc610e9da95df597b9464628680",uri="sip:192.168.18.201:5060",response="7c2777abebc0271b9fb2fd9b3348b72c",algorithm=MD5
    Max-Forwards: 70
    From: <sip:10003@192.168.18.201>;tag=7099fb862c
    To: <sip:10003@192.168.18.201>
    Call-ID: b8aedf5d1bb1c1ed
    CSeq: 16311 REGISTER
    Contact: <sip:10003@192.168.18.209:5063>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] > 440 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5060;branch=z9hG4bKe48391c772a739eb7
    Max-Forwards: 70
    From: <sip:10000@192.168.18.201>;tag=7a9bfa75ce
    To: <sip:10000@192.168.18.201>
    Call-ID: 162f19e419fcc3b6
    CSeq: 10211 REGISTER
    Contact: <sip:10000@192.168.18.209:5060>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] < 355 Stack: from 192.168.18.201
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.18.209:5063;branch=z9hG4bKa01b6a19714604d89
    Contact: <sip:10003@192.168.18.209:5063>;expires=300
    To: <sip:10003@192.168.18.201>;tag=0c1da918
    From: <sip:10003@192.168.18.201>;tag=7099fb862c
    Call-ID: b8aedf5d1bb1c1ed
    CSeq: 16311 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] < 453 Stack: from 192.168.18.201
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.18.209:5060;branch=z9hG4bKe48391c772a739eb7
    Proxy-Authenticate: Digest nonce="414d535c0c56446215:63bf1b8dfb3d4ecf16452a51155646ea",algorithm=MD5,realm="3CXPhoneSystem"
    To: <sip:10000@192.168.18.201>;tag=ca04c424
    From: <sip:10000@192.168.18.201>;tag=7a9bfa75ce
    Call-ID: 162f19e419fcc3b6
    CSeq: 10211 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] > 657 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5060;branch=z9hG4bK99c00bd016d4e1542
    Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",nonce="414d535c0c56446215:63bf1b8dfb3d4ecf16452a51155646ea",uri="sip:192.168.18.201:5060",response="729f015cbde9f25177be430d565523c2",algorithm=MD5
    Max-Forwards: 70
    From: <sip:10000@192.168.18.201>;tag=7a9bfa75ce
    To: <sip:10000@192.168.18.201>
    Call-ID: 162f19e419fcc3b6
    CSeq: 10212 REGISTER
    Contact: <sip:10000@192.168.18.209:5060>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:14:59 SIP_TR> [STACK] < 355 Stack: from 192.168.18.201
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.18.209:5060;branch=z9hG4bK99c00bd016d4e1542
    Contact: <sip:10000@192.168.18.209:5060>;expires=300
    To: <sip:10000@192.168.18.201>;tag=aa0dc22c
    From: <sip:10000@192.168.18.201>;tag=7a9bfa75ce
    Call-ID: 162f19e419fcc3b6
    CSeq: 10212 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] > 440 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5061;branch=z9hG4bK1d7acc2570000c1b7
    Max-Forwards: 70
    From: <sip:10001@192.168.18.201>;tag=dd75418d6a
    To: <sip:10001@192.168.18.201>
    Call-ID: b12dabfb324fab4e
    CSeq: 31149 REGISTER
    Contact: <sip:10001@192.168.18.209:5061>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] < 453 Stack: from 192.168.18.201
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.18.209:5061;branch=z9hG4bK1d7acc2570000c1b7
    Proxy-Authenticate: Digest nonce="414d535c0c56446742:331088ca7a5a0a60e418b1cf863c25d3",algorithm=MD5,realm="3CXPhoneSystem"
    To: <sip:10001@192.168.18.201>;tag=ed19797b
    From: <sip:10001@192.168.18.201>;tag=dd75418d6a
    Call-ID: b12dabfb324fab4e
    CSeq: 31149 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] > 657 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5061;branch=z9hG4bK8f88c65c7a3896c3c
    Proxy-Authorization: Digest username="10001",realm="3CXPhoneSystem",nonce="414d535c0c56446742:331088ca7a5a0a60e418b1cf863c25d3",uri="sip:192.168.18.201:5060",response="a84bf0d135fa0c9e28b26fbfa2c0fb58",algorithm=MD5
    Max-Forwards: 70
    From: <sip:10001@192.168.18.201>;tag=dd75418d6a
    To: <sip:10001@192.168.18.201>
    Call-ID: b12dabfb324fab4e
    CSeq: 31150 REGISTER
    Contact: <sip:10001@192.168.18.209:5061>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] < 355 Stack: from 192.168.18.201
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.18.209:5061;branch=z9hG4bK8f88c65c7a3896c3c
    Contact: <sip:10001@192.168.18.209:5061>;expires=300
    To: <sip:10001@192.168.18.201>;tag=04680f58
    From: <sip:10001@192.168.18.201>;tag=dd75418d6a
    Call-ID: b12dabfb324fab4e
    CSeq: 31150 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] > 440 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5062;branch=z9hG4bK8300f1da8dc453e2a
    Max-Forwards: 70
    From: <sip:10002@192.168.18.201>;tag=a73d77c023
    To: <sip:10002@192.168.18.201>
    Call-ID: 89b0221c508ce323
    CSeq: 23108 REGISTER
    Contact: <sip:10002@192.168.18.209:5062>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] < 453 Stack: from 192.168.18.201
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.18.209:5062;branch=z9hG4bK8300f1da8dc453e2a
    Proxy-Authenticate: Digest nonce="414d535c0c56446883:541414a1c93aeeb68a3b2470e853c73c",algorithm=MD5,realm="3CXPhoneSystem"
    To: <sip:10002@192.168.18.201>;tag=e14b8153
    From: <sip:10002@192.168.18.201>;tag=a73d77c023
    Call-ID: 89b0221c508ce323
    CSeq: 23108 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0


    11:15:04 SIP_TR> [STACK] > 657 Stack: to 192.168.18.201
    REGISTER sip:192.168.18.201:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.18.209:5062;branch=z9hG4bK3fb23fcc747a6377e
    Proxy-Authorization: Digest username="10002",realm="3CXPhoneSystem",nonce="414d535c0c56446883:541414a1c93aeeb68a3b2470e853c73c",uri="sip:192.168.18.201:5060",response="aa147f30aa1b24e2a19f35c446ef5c8b",algorithm=MD5
    Max-Forwards: 70
    From: <sip:10002@192.168.18.201>;tag=a73d77c023
    To: <sip:10002@192.168.18.201>
    Call-ID: 89b0221c508ce323
    CSeq: 23109 REGISTER
    Contact: <sip:10002@192.168.18.209:5062>
    Expires: 300
    User-Agent: Patton SN4114 JO EUI 00A0BA0B7748 R6.8 2015-07-09 H323 SIP FXS FXO M5T SIP Stack/4.2.8.10
    Content-Length: 0


    11:15:05 SIP_TR> [STACK] < 355 Stack: from 192.168.18.201
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.18.209:5062;branch=z9hG4bK3fb23fcc747a6377e
    Contact: <sip:10002@192.168.18.209:5062>;expires=300
    To: <sip:10002@192.168.18.201>;tag=c422ea71
    From: <sip:10002@192.168.18.201>;tag=a73d77c023
    Call-ID: 89b0221c508ce323
    CSeq: 23109 REGISTER
    User-Agent: 3CXPhoneSystem 12.0.41311.996 (34969)
    Content-Length: 0
     
  11. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    Sorry, forget that you were using a gateway and not a VoIP provider.

    Since you get a busy signal when calling your outside number, then (at least) one of your lines is being seized, possibly by the gateway. Are you using a pilot number with a hunt option from your PSTN provider? Perhaps it is just the first line that is busy. Did you unplug all PSTN lines from the gateway and confirm that you can receive calls (using a standard phone) , on all lines? There is a possibility that one line is shorted somewhere (why you are getting busy) and on outgoing, isn't selected by the gateway. Of course, in a hunt situation, the call should move to the next line. there is also a possibility that one port on the gateway is faulty, or provisioned incorrectly.
     
  12. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Here is a screen shot. I've also disabled stun to see if that helps. No change. Ext 800 rings to extension 100 front desk and 400 manager office. These go to the to yealink Sip-T46G. We tested the PSTN lines going out, but i'm not sure about coming in. I will check tomorrow a.m. Looking in the FXO Status in the Pattons.
    2 ports say:

    Slot: 0
    Number of Ports: 4

    Silab Port: 0 0
    ---------------

    Line State: Up
    Line Polarity: Negative
    State: OnHook

    Driver information
    Si3050 Rev: 5
    Si3019 Rev: 6
    Line Voltage: -44V
    Line Current: 0mA


    2ports say:

    Slot: 0
    Number of Ports: 4

    Silab Port: 0 1
    ---------------

    Line State: Up
    Line Polarity: Positive
    State: OnHook

    Driver information
    Si3050 Rev: 5
    Si3019 Rev: 6
    Line Voltage: 45V
    Line Current: 0mA
     

    Attached Files:

    • in.png
      in.png
      File size:
      160 KB
      Views:
      922
    • in2.png
      in2.png
      File size:
      185 KB
      Views:
      922
  13. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    The 3CX setting (for incoming) won't be coming into play at this point as you are not even getting a log of an incoming call. The Patton information tells me that tip and ring are reversed on one of the lines, but that should not be causing a busy signal on incoming calls. You may have to determine if the busy signal is coming from your PSTN provider (the line is actually seen as in use), or, the Patton is answering and for some reason, is sending the caller to a busy signal (internally) because it is unable to process it.
     
  14. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    Stupid question have you opened a ticket with Patton and given them a call?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. cdubb79

    Joined:
    Nov 6, 2015
    Messages:
    8
    Likes Received:
    0
    Well I followed what you said. I followed up with the phone guy and asked again if he checked that the inbound was working from the Cisco router. He said yes. I went onsite and tested it myself. Unplug all data and voice devices on the Lan and calls were still going to a busy signal. I called Winstream. Apparently the router was not configured properly by Winstream. They took 2 days to figure it out. It was missing one line of code. Problem solved. Sorry to waste your time.
     
  16. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,084
    Likes Received:
    325
    As far as I'm concerned, you didn't waste my time. If anyone's time was wasted it was yours, by Winstream, that didn't do the job properly to begin with. I'm glad it all worked out in the end.
     
Thread Status:
Not open for further replies.