Audio Issue

Discussion in '3CX Phone System - General' started by shatty, Jun 12, 2012.

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

    Joined:
    Dec 4, 2008
    Messages:
    28
    Likes Received:
    0
    Aside from the other problems I am having, the most important one is audio issues. When I receive a call, I can not hear the other person. Firewall check passes without an error. I have ports 9000-9050 tcp/udp forwarded as was as 5060 tcp/udp forwarded. Logs said can not communicate with stun servers. All 3 of them. So i was advised to disable stun server and specify public IP. That fixed the incoming calls so far. But when making an outgoing call, I can not hear the other person but they can here me. In the logs it says "busy" or "busy here" Any ideas?
     
  2. shatty

    Joined:
    Dec 4, 2008
    Messages:
    28
    Likes Received:
    0
    11:37:04.945|Call.cpp(1470)|Log2||Call::Terminate:[CM503008]: Call(17): Call is terminated<br>
    11:37:08.555|Call.cpp(42)|Log3||??:Currently active calls - 1: [18]<br>
    11:37:13.337|CallCtrl.cpp(348)|Log2||CallCtrl::eek:nIncomingCall:[CM503001]: Call(19): Incoming call from Ext.252 to <sip:17187485975@192.168.1.20><br>
    11:37:13.338|Extension.cpp(1421)|Log3||Extension::printEndpointInfo:[CM505001]: Ext.252: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA508G-7.5.1a] PBX contact: [sip:252@192.168.1.20:5060]<br>
    11:37:13.338|CallCtrl.cpp(540)|Log3||CallCtrl::eek:nSelectRouteReq:[CM503010]: Making route(s) to <sip:17187485975@192.168.1.20><br>
    11:37:13.338|CallCtrl.cpp(730)|Log2||CallCtrl::eek:nSelectRouteReq:[CM503004]: Call(19): Route 1: VoIPline:17187485975@(Ln.10000@Nexvortex - US)@[Dev:sip:nP8884Amgj@66.23.129.253:5060]<br>
    11:37:13.388|Target.cpp(446)|Log2||Target::makeOneInvite:[CM503025]: Call(19): Calling VoIPline:17187485975@(Ln.10000@Nexvortex - US)@[Dev:sip:nP8884Amgj@66.23.129.253:5060]<br>
    11:37:25.428|CallLeg.cpp(316)|Log3||CallLeg::eek:nAnswer:[CM503002]: Call(19): Alerting sip:nP8884Amgj@66.23.129.253:5060<br>
    11:37:25.428|Line.cpp(1461)|Log2||Line::printEndpointInfo:[CM505003]: Provider:[Nexvortex - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:nP8884Amgj@108.6.54.34:5060]<br>
    11:37:27.472|CallLeg.cpp(327)|Log2||CallLeg::eek:nFailure:[CM503003]: Call(19): Call to sip:17187485975@66.23.129.253:5060 has failed; Cause: 486 Busy Here; from IP:66.23.129.253:5060<br>
    11:37:27.472|Call.cpp(1154)|Log2||Call::RouteFailed:[CM503016]: Call(19): Attempt to reach <sip:17187485975@192.168.1.20> failed. Reason: Busy<br>
    11:37:27.472|Call.cpp(648)|Log2||Call::DoEndCall:[CM503020]: Normal call termination. Reason: Busy<br>
    11:37:38.557|Call.cpp(42)|Log3||??:Currently active calls - 1: [18]<br>
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,737
    Likes Received:
    278
    Are you able to ping the STUN servers? Could it be a DNS server setting? That indicate that there is a problem and that you may just be ignoring it at your peril. The fact that you have no audio may be a result of disabling STUN, or may be related to the same reason that STUN fails.

    s
    Seems to indicate that your provider is sending back the busy message.
     
  4. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    522
    Likes Received:
    12
    Related to STUN... check for port 3478 (TCP and UDP) on your firewall...
     
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    It appears that you are using nexVortex as your carrier. How long has this install been in-place? Is this anew issue or something that just cropped up? You should not need STUN to accommodate nexVortex. did you use the in-built provisioning template or manually provision? Do you have PBX provides audio checked for nexVortex? It should be.
     
Thread Status:
Not open for further replies.