Call failing one way to extension

Discussion in '3CX Phone System - General' started by andrew_h, Apr 28, 2010.

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

    Joined:
    Apr 28, 2010
    Messages:
    3
    Likes Received:
    0
    Ok, so i have 3cx installed working with a SPA-3102 as a gateway and an Engin SIP account.

    I have 2 phones, one is a Avaya desk phone (x500), the other is a Nokia E51 (x501) connected wirelessly as a SIP client.

    Incoming calls via both Voip and PSTN are routed through to both phones in a group - Works fine
    The E51 can call the Desk phone no problems but for some reason the desk phone can not call the E51 and i have no idea why.

    Log entries:
    Code:
    09:30:42.095  [CM503008]: Call(231): Call is terminated
    09:30:42.033  [CM503020]: Normal call termination. Reason: No answer
    09:30:42.033  [CM503016]: Call(231): Attempt to reach "501"<sip:501@192.168.1.253> failed. Reason: No Answer
    09:30:42.033  [CM503003]: Call(231): Call to sip:501@192.168.1.253 has failed; Cause: 408 Request Timeout; internal
    09:30:09.923  [CM503025]: Call(231): Calling Ext:Ext.501@[Dev:sip:501@192.168.1.6:5060;transport=UDP]
    09:30:09.861  [CM503004]: Call(231): Route 1: Ext:Ext.501@[Dev:sip:501@192.168.1.6:5060;transport=UDP]
    09:30:09.861  [CM503010]: Making route(s) to "501"<sip:501@192.168.1.253>
    09:30:09.861  [CM505001]: Ext.500: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Avaya SIP R2.2 Endpoint Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26] PBX contact: [sip:500@192.168.1.253:5060]
    09:30:09.861  [CM503001]: Call(231): Incoming call from Ext.500 to "501"<sip:501@192.168.1.253>
    
    Can somone explain this?

    One thing that might have something to do with it is in the initial setup, i set the extension range to start at 100. As it turns out, this was no good so i have manually changed the extensions to 500, 501 etc. I could not find a 'propper' way to change the start of the range other than to re-install the whole lot.
     
  2. bluetel2

    bluetel2 Member

    Joined:
    Oct 16, 2008
    Messages:
    377
    Likes Received:
    6
    Hi,

    try to change spa-3102 port on line1 config admin and sip port to 5065.

    try this and said result
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. andrew_h

    Joined:
    Apr 28, 2010
    Messages:
    3
    Likes Received:
    0
    Thankyou for your response but i am not having problems with the 3102 or any external calls. It is working fine for incoming and outgoing calls from/to both extensions. The problem i am having is local calls between the extensions.

    For some reason 501 -> 500 works (E51 to Avaya) but 500 -> 501 does not work (avaya to E51), it produces the error i have above in the logs.
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,367
    Likes Received:
    228
    It looks like 3CX can't find Ext 501....

    So, I would think that 501 either isn't registered (properly?) or is not responding to the call. Does it show in 3CX as being registered?

    What does the 3CX log look like when you turn on Nokia and it first registers?
     
  5. andrew_h

    Joined:
    Apr 28, 2010
    Messages:
    3
    Likes Received:
    0
    Code:
    22:14:19.127  [CM504001]: Ext.501: new contact is registered. Contact(s): [sip:501@192.168.1.6:5060;transport=UDP/501]
    
    It appears to be registered fine - green light etc. I would have thought that if it was not, then it would not work for incoming calls from external sources but it is. That is what has me baffled.
     
Thread Status:
Not open for further replies.