Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

SPA-3102 VOIP-to-PSTN problem

Discussion in '3CX Phone System - General' started by pani, Feb 26, 2008.

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

    Joined:
    Feb 26, 2008
    Messages:
    2
    Likes Received:
    0
    Hi,

    I've looked through all the help in this forum for my problem but nothing I have read has fixed it.

    I can receive calls from PSTN through Linksys SPA-3102 to VOIP.

    I can not make calls from VOIP through the Linksys to PSTN.

    The error in the log is:

    16:43:20.229 Call::Terminate [CM503008]: Call(51): Call is terminated
    16:43:20.198 Call::RouteFailed [CM503014]: Call(51): Attempt to reach [sip:8105@192.168.0.10] failed. Reason: Server Failure
    16:43:20.198 CallLeg::eek:nFailure [CM503003]: Call(51): Call to sip:105@192.168.0.20:5060 has failed; Cause: 503 Service Unavailable; from IP:192.168.0.20:5060
    16:43:20.151 MediaServerReporting::SetRemoteParty [MS210006] C:51.2:Offer provided. Connection(by pass mode): 192.168.0.25:60000(60001)
    16:43:20.120 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(51): Calling: PSTNline:10001@[Dev:sip:10001@192.168.0.20:5060]
    16:43:20.104 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:8105@192.168.0.10]
    16:43:20.104 MediaServerReporting::SetRemoteParty [MS210000] C:51.1:Offer received. RTP connection: 192.168.0.25:60000(60001)
    16:43:20.104 CallLeg::setRemoteSdp Remote SDP is set for legC:51.1
    16:43:20.104 Extension::printEndpointInfo [CM505001]: Ext.104: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CMI CM5K] Transport: [sip:192.168.0.10:5060]
    16:43:20.089 CallCtrl::eek:nIncomingCall [CM503001]: Call(51): Incoming call from Ext.104 to [sip:8105@192.168.0.10]
    16:43:20.089 CallLeg::eek:nNewCall [CM500002]: Info on incoming INVITE:
    INVITE sip:8105@192.168.0.10 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.25:5060;rport=5060;branch=z9hG4bK1cb44c31b714c801a1ee360a58de5509
    Max-Forwards: 70
    Contact: [sip:104@192.168.0.25:5060]
    To: [sip:8105@192.168.0.10]
    From: "104"[sip:104@192.168.0.10];tag=490057ec
    Call-ID: 22fda18f3979c53b6983c1f74933753f@192.168.0.25
    CSeq: 802 INVITE
    Allow: INVITE, CANCEL, ACK, BYE, NOTIFY, REFER, OPTIONS, INFO, MESSAGE
    Proxy-Authorization: Digest username="104",realm="3CXPhoneSystem",nonce="12848517799:d6612554064966ab07a8ecf11769c3b0",response="d9bd5ab09ef21ec8c04bd3a7821bf901",uri="sip:8105@192.168.0.10",algorithm=MD5
    User-Agent: CMI CM5K
    Content-Length: 0


    You'll see I'm dialing 8105, and the intended number I want to call is 105 - so it taking off the first digit as I wanted. 105 is a weird number to dial but trust me that number, if dialed direct on the wall socket goes through to the number I want it to, so when I dial 8105 on a VOIP phone and it sends across 105 that is accurate.

    I either get a 404 error, or a 503 error. On the Linksys the PSTN and Line 1 ports are not the same port, and the I have updated the the port in 3cx in the line gateway setup.

    I tried to telnet to the Linksys on port 5060 and 5061 and it doesn't respond, yet it seems to through 3cx - don't know if that is important or not.

    I've tried everything - can anyone help? Not sure if the error lies in 3cx or Linksys, although I presume linksys.

    Thanks in advance.

    Pani
     
  2. Wardy

    Wardy New Member

    Joined:
    Sep 18, 2007
    Messages:
    110
    Likes Received:
    0
    Try setting the linksys and 3cx to use 5061 you can do this in the web interface for the Linksys (http://xxx.xxx.xxx.xxx/admin/voice/advanced) and select PSTN line.
    Then under Manage Gateways in 3CX select the PSTN Line and set the Gateway port to 5061

    Stephen
     
  3. pani

    Joined:
    Feb 26, 2008
    Messages:
    2
    Likes Received:
    0
    Thanks Stephen

    I have already tried that and I'm really lost to what the problem might be.

    Any other suggestions I should try?

    Pani
     
  4. Wardy

    Wardy New Member

    Joined:
    Sep 18, 2007
    Messages:
    110
    Likes Received:
    0
    I will post screen shots of my set up soon but in the mean time are you using the ATA function if not I had to ensure that Line 1 was disabled

    Stephen
     
  5. rikalps

    Joined:
    Mar 9, 2008
    Messages:
    1
    Likes Received:
    0
    Same problem, tried all configurations found in 3cx site and in this forum
    incoming calls work fine, outgoing calls connect and in one second close connection,

    log is this:

    12:20:42.953 Call::Terminate [CM503008]: Call(21): Call is terminated
    12:20:42.953 Call::Terminate [CM503008]: Call(21): Call is terminated
    12:20:42.734 CallCtrl::eek:nLegConnected [CM503007]: Call(21): Device joined: sip:10002@192.168.1.241:5060
    12:20:42.718 CallCtrl::eek:nLegConnected [CM503007]: Call(21): Device joined: sip:14@192.168.1.48:5060;rinstance=6616a778c96b7720
    12:20:42.703 Line::printEndpointInfo [CM505002]: Gateway:[SPA_3102_GATEWAY] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.5(GWa)] Transport: [sip:192.168.1.240:5060]
    12:20:42.593 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(21): Calling: PSTNline:10002@[Dev:sip:10002@192.168.1.241:5060]
    12:20:42.578 CallCtrl::eek:nIncomingCall [CM503001]: Call(21): Incoming call from Ext.14 to [sip:9337750801@192.168.1.240:5060]
    12:15:31.437 StunClient::loadStunList [CM306002]: There is no valid STUN server specified! External IP can not be resolved.
    11:55:31.359 StunClient::loadStunList [CM306002]: There is no valid STUN server specified! External IP can not be resolved.
    11:53:02.390 Call::Terminate [CM503008]: Call(20): Call is terminated
    11:53:02.375 Call::RouteFailed [CM503014]: Call(20): Attempt to reach [sip:9337750801@192.168.1.240:5060] failed. Reason: Not Found
    11:53:02.375 CallLeg::eek:nFailure [CM503003]: Call(20): Call to sip:337750801@192.168.1.241:5060 has failed; Cause: 410 Gone; from IP:192.168.1.241:5060
    11:53:01.328 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(20): Calling: PSTNline:10002@[Dev:sip:10002@192.168.1.241:5060]
    11:53:01.312 CallCtrl::eek:nIncomingCall [CM503001]: Call(20): Incoming call from Ext.14 to [sip:9337750801@192.168.1.240:5060]
    11:48:55.515 Call::Terminate [CM503008]: Call(19): Call is terminated
    11:48:55.515 Call::Terminate [CM503008]: Call(19): Call is terminated
    11:48:55.281 CallCtrl::eek:nLegConnected [CM503007]: Call(19): Device joined: sip:10002@192.168.1.241:5060
    11:48:55.265 CallCtrl::eek:nLegConnected [CM503007]: Call(19): Device joined: sip:14@192.168.1.48:5060;rinstance=6616a778c96b7720
    11:48:55.265 Line::printEndpointInfo [CM505002]: Gateway:[SPA_3102_GATEWAY] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.5(GWa)] Transport: [sip:192.168.1.240:5060]
    11:48:55.156 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(19): Calling: PSTNline:10002@[Dev:sip:10002@192.168.1.241:5060]
    11:48:55.140 CallCtrl::eek:nIncomingCall [CM503001]: Call(19): Incoming call from Ext.14 to [sip:9337750801@192.168.1.240:5060]

    why says device info: "Device Not Identified: User Agent not matched"
    what does it mean?

    status line show line is registered
    pls help!
     
Thread Status:
Not open for further replies.