Incomming calls fail; Device Not Identified error

Discussion in '3CX Phone System - General' started by MikeMSTG, Oct 21, 2014.

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

    Joined:
    Oct 21, 2014
    Messages:
    3
    Likes Received:
    0
    Incoming phone calls are getting this error message:

    21-Oct-2014 14:17:39.834 [CM505003]: Provider:[Broadvox Fusion (IP Based) - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Broadvox Fusion] PBX contact: [sip:xxxxxxxxxx@xxx.xxx.xxx.xxx:5060]

    The caller will hear "call transfer failed" message.

    The odd part is this typically only happens after a longer period of time of no phone calls. If I were to make an outgoing phone call and then receive one, no problem.

    We are configured with a direct IP so we do not require in/out registration. I have configured Source identification by DID. I am on the latest and greatest version of 3cx.

    Anyone know why this is happening?
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    I seem to recall seeing
    often, even on working calls. So...I'm not sure that is the issue. I think that additional logs are needed, something showing an error, or call rejection.
     
  3. MikeMSTG

    Joined:
    Oct 21, 2014
    Messages:
    3
    Likes Received:
    0
    Here is the full log of the call:
    22-Oct-2014 11:32:31.856 [CM505003]: Provider:[Broadvox Fusion (IP Based) - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Broadvox Fusion] PBX contact: [sip:xxxxxxxxxx@xxx.xxx.xxx.xxx:5060]
    22-Oct-2014 11:32:31.856 Leg L:2.3[Extn] is terminated: Cause: 503 No matching transport found/INVITE from local
    22-Oct-2014 11:32:31.856 L:2.1[Line:10000<<xxxxxxxxxx] failed to reach Extn:1234, reason Server Failure
    22-Oct-2014 11:32:31.856 Call to T:Extn:1234@[Dev:sip:1234@192.168.xxx.xxx:5060] from L:2.1[Line:10000<<xxxxxxxxxx] failed, cause: Cause: 503 No matching transport found/INVITE from local
    22-Oct-2014 11:32:31.856 [CM503003]: Call(C:2): Call to <sip:1234@192.168.xxx.xxx:5060> has failed; Cause: 503 No matching transport found/INVITE from local
    22-Oct-2014 11:32:31.756 [CM503025]: Call(C:2): Calling T:Extn:1234@[Dev:sip:1234@192.168.xxx.xxx:5060] for L:2.1[Line:10000<<xxxxxxxxxx]
    22-Oct-2014 11:32:31.703 [CM503027]: Call(C:2): From: Line:10000<<xxxxxxxxxx ("Main Number:xxxxxxxxxx" <sip:xxxxxxxxxx@192.168.xxx.xxx:5060>) to T:Extn:1234@[Dev:sip:1234@192.168.xxx.xxx:5060]
    22-Oct-2014 11:32:31.703 [CM503004]: Call(C:2): Route 1: from L:2.1[Line:10000<<xxxxxxxxxx] to T:Extn:1234@[Dev:sip:1234@192.168.xxx.xxx:5060]
    22-Oct-2014 11:32:31.703 [CM505003]: Provider:[Broadvox Fusion (IP Based) - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Broadvox Fusion] PBX contact: [sip:xxxxxxxxxx@xxx.xxx.xxx.xxx:5060]
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    Well this is the problem...

    I'm not certain if is is a network (UDP/TCP) setting (Codec?).

    Did this just start, or did you make some changes.

    I thought this sounded familiar... http://www.3cx.com/forums/cisco-spa504g-always-busy-or-not-available-38654-s15.html
     
  5. MikeMSTG

    Joined:
    Oct 21, 2014
    Messages:
    3
    Likes Received:
    0
    Same issue...never got anywhere with it.

    We checked the network setup and all was clear. We also contacted our provider and confirmed that the calls are connecting to our side without issue. As best I can tell, the issue is with 3cx, whether it be setup or phone support, it is most likely on the PBX side.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    An intermittent problem is the worst thing to troubleshoot. Do you have any other VoIP providers, or have you ever used any other VoIP providers that this has, or has not, happened on?

    The best you could probably hope for is another user that has the same provider, and can provide trunk settings to compare with.
    Hopefully one that isn't having the same issue.

    You could delve a bit deeper using Wireshark. There may also be some additional, helpful, information if you use the verbose logs setting.
     
Thread Status:
Not open for further replies.