Windows Update + 503 No matching transport found/INVITE from local

Discussion in '3CX Phone System - General' started by neon013, Nov 12, 2015.

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

    Joined:
    Dec 16, 2013
    Messages:
    2
    Likes Received:
    0
    A couple of days ago our 3CX phone system worked fine. We have several buildings connected over VPN and hence several extensions at different locations - and all worked OK both for external and internal calls. Over the evening I allowed some 30+ updates to take place on our Windows 2008 server. I am guessing that from one of these updates our 3CX system was affected in the following way:-

    No external or internal calls can be made to the site which has the server, although the server serves all sites. At the moment I have had to redirect all external calls to another site to receive the call.

    On reviewing the logs (see below - example is an internal call from extension 111 (Home) to extension 191 (location of server) :-

    12-Nov-2015 11:58:52.356 Leg L:99.1[Extn] is terminated: Cause: BYE from PBX
    12-Nov-2015 11:58:52.305 Leg L:99.2[Extn] is terminated: Cause: 503 No matching transport found/INVITE from local
    12-Nov-2015 11:58:52.302 [CM503020]: Call(C:99): Normal call termination. Call originator: Extn:111. Reason: Server Failure
    12-Nov-2015 11:58:52.302 L:99.1[Extn] failed to reach Extn:191, reason Server Failure
    12-Nov-2015 11:58:52.302 Call to T:Extn:191@[Dev:sip:191@192.168.19.12:5060] from L:99.1[Extn] failed, cause: Cause: 503 No matching transport found/INVITE from local
    12-Nov-2015 11:58:52.302 [CM503003]: Call(C:99): Call to <sip:191@leapfrog-merlin:5060> has failed; Cause: 503 No matching transport found/INVITE from local
    12-Nov-2015 11:58:52.252 [CM503025]: Call(C:99): Calling T:Extn:191@[Dev:sip:191@192.168.19.12:5060] for L:99.1[Extn]
    12-Nov-2015 11:58:52.203 [CM503027]: Call(C:99): From: Extn:111 ("HomeDottty" <sip:111@leapfrog-merlin:5060>) to T:Extn:191@[Dev:sip:191@192.168.19.12:5060]
    12-Nov-2015 11:58:52.203 [CM503004]: Call(C:99): Route 1: from L:99.1[Extn] to T:Extn:191@[Dev:sip:191@192.168.19.12:5060]
    12-Nov-2015 11:58:52.201 [CM503001]: Call(C:99): Incoming call from Extn:111 to sip:191@leapfrog-merlin:5060


    Additionally when trying to reproduce the problem and get the above log – it worked for a few calls only! - Log below is 25 minutes earlier but I have no idea why it worked for a short time period.

    12-Nov-2015 11:33:07.467 Leg L:80.1[Extn] is terminated: Cause: BYE from 192.168.1.12:5060
    12-Nov-2015 11:32:52.774 [CM503007]: Call(C:80): Extn:113 has joined, contact <sip:113@192.168.1.12:5060>
    12-Nov-2015 11:32:52.772 L:80.2[Extn] has joined to L:80.1[Extn]
    12-Nov-2015 11:32:50.134 [CM503025]: Call(C:80): Calling T:Extn:191@[Dev:sip:191@192.168.19.12:5060] for L:80.1[Extn]
    12-Nov-2015 11:32:50.087 [CM503027]: Call(C:80): From: Extn:113 ("HomeNeil" <sip:113@leapfrog-merlin:5060>) to T:Extn:191@[Dev:sip:191@192.168.19.12:5060]
    12-Nov-2015 11:32:50.086 [CM503004]: Call(C:80): Route 1: from L:80.1[Extn] to T:Extn:191@[Dev:sip:191@192.168.19.12:5060]
    12-Nov-2015 11:32:50.084 [CM503001]: Call(C:80): Incoming call from Extn:113 to <sip:191@leapfrog-merlin:5060>


    Please advise if you have any ideas – is the Windows Update a red herring?
     
  2. nikosT_3cx

    3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    57
    Likes Received:
    0
    Hi,

    please open a ticket on our Support portal and provide us the logs of the Phone System in order to check them and find what is causing the termination of the call.
     
Thread Status:
Not open for further replies.