No Answer problem

Discussion in '3CX Phone System - General' started by bigsiqc, Dec 4, 2007.

  1. bigsiqc

    Joined:
    Nov 21, 2007
    Messages:
    23
    Likes Received:
    0
    I have a Grandstream 4104 (IP:192.168.0.160)and 3cx v3 running on 192.168.0.23.

    When the PSTN lines ring in they are routed to ext 107. This is set to ring a call group (800)if it is not answered in 15 seconds.

    When the call rings the group it does so for less than a second the redirects to ext 107.

    here is the Log

    19:58:34.203 StratInOut::eek:nHangUp [CM104007] Call(41): Call Ln:10001@grandstream to 800 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160
    19:58:25.718 CallConf::eek:nProvisional [CM103003] Call(41): Ext.107 is ringing
    19:58:25.453 CallConf::eek:nIncoming [CM103002] Call(41): Incoming call from unknown (Ln:10001@grandstream) to sip:1001@192.168.0.23:5060
    19:58:19.765 StratInOut::eek:nHangUp [CM104007] Call(40): Call from Ln:10001@grandstream to 101 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160
    19:58:04.656 CallConf::eek:nProvisional [CM103003] Call(40): Ext.107 is ringing

    I have tried diverting it to an extension and the sameapplies.

    Help please

    Thanks

    Simon
     
  2. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Good afternoon

    Sorry to paraphrase but I want to be sure we understand.

    1. A call comes in on your PSTN
    2. The call is routed to Extension 107
    3. The call rings extension 107.
    4. After being unanswered for 15 seconds the call is routed to Ring Group 800.
    5. After ringing the Ring Group for 1 second it is routed back to extension 107.

    Is 1-5 above correct?

    What extensions are members of the Ring Group? Is extension 107 a member of the ring group? What are the options you have set if the Ring Group is unanswered? How long do you have it set to ring the ring group?

    Take care
     
  3. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    Actually, according to logs the call has been canceled by Grandstream even before that 15 seconds passed (34 - 25 = 9). So PBX didn't even have a chance to forward it to RG
     
  4. bigsiqc

    Joined:
    Nov 21, 2007
    Messages:
    23
    Likes Received:
    0
    Thanks ralph - that is a very clear summary.

    extensions 101, 102, 103 and 104 are members of the ring group. the group is set to continue ringing if there is no answer and it is set to ring for 90 seconds.
     
  5. bigsiqc

    Joined:
    Nov 21, 2007
    Messages:
    23
    Likes Received:
    0
    Yes the grandstrea is cancelling it but there is a blip when the other groups ring. do you think that this a problem with the grandstream?

    Thanks

    Simon
     
  6. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Interesting

    I have to agree with Archie. According to the logs you posted it does appear that the Grandstream is canceling the call before any transfers occur.

    If the transfers are actually happening are these the correct logs that cover the period over which they happen?
     
  7. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    hello again

    You may want to check your configuration settings on the Grandstream.
     
  8. bigsiqc

    Joined:
    Nov 21, 2007
    Messages:
    23
    Likes Received:
    0
    Here is the latest log

    20:50:13.311 StratInOut::eek:nHangUp [CM104007] Call(63): Call from Ln:10001@grandstream to 107 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160
    20:50:05.265 CallConf::eek:nProvisional [CM103003] Call(63): Ext.107 is ringing
    20:50:05.046 CallConf::eek:nIncoming [CM103002] Call(63): Incoming call from unknown (Ln:10001@grandstream) to sip:10001@192.168.0.23:5060
    20:49:59.390 StratInOut::eek:nHangUp [CM104007] Call(62): Call from Ln:10001@grandstream to 101 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160
    20:49:44.265 CallConf::eek:nProvisional [CM103003] Call(62): Ext.107 is ringing
    20:49:44.046 CallConf::eek:nIncoming [CM103002] Call(62): Incoming call from unknown (Ln:10001@grandstream) to sip:10001@192.168.0.23:5060
    20:49:38.405 StratInOut::eek:nHangUp [CM104007] Call(61): Call from Ln:10001@grandstream to 101 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160
    20:49:23.265 CallConf::eek:nProvisional [CM103003] Call(61): Ext.107 is ringing
    20:49:23.030 CallConf::eek:nIncoming [CM103002] Call(61): Incoming call from unknown (Ln:10001@grandstream) to sip:10001@192.168.0.23:5060

    I know it looks like no extensions ring but I am showing a missed call at exactly the right time on my eyebeam.

    Regards

    Simon
    Thanks for the help!
     
  9. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Interesting

    It looks to me like the call is comming from the Grandstream to ext 107 and that the extension is ringing but then the Grandstream cancels the call.

    I have reversed the order to make it easier to follow:

    1. Call comes in from Grandstream:
    20:49:23.030 CallConf::eek:nIncoming [CM103002] Call(61): Incoming call from unknown (Ln:10001@grandstream) to sip:10001@192.168.0.23:5060

    2.Extension 107 starts to be rung:
    20:49:23.265 CallConf::eek:nProvisional [CM103003] Call(61): Ext.107 is ringing

    3. Call is canceled by Grandstream device:
    20:49:38.405 StratInOut::eek:nHangUp [CM104007] Call(61): Call from Ln:10001@grandstream to 101 has been terminated by Ln:10001@grandstream; cause: CANCEL; from IP:192.168.0.160

    I notice that the cancel event states that "to 101 has been terminated" which would seem to indicate that a transfer to the ring group (ext 101-104) has occurred?

    So if the call transfers to and rings 107 properly and the initial transfer to the ring group happens why is the call dropped the second it rings the ring group?

    Is there a setting on the Grandstream that could account for this? Maybe it can't re-invite??

    Do you have your log settings on verbose so we can get a more detailed set of logs to work from?
     
  10. bigsiqc

    Joined:
    Nov 21, 2007
    Messages:
    23
    Likes Received:
    0
    Hi Ralph and Archie.

    I have just borrowed another 4104 from my neighbour and it is working fine on all the same settings. I can only conclude that this is a hardware failure.

    thanks for all your help

    Simon
     

Share This Page