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.

Tunneled hardphone generates one-way audio

Discussion in 'Windows' started by Ryandc, Jun 27, 2008.

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

    Joined:
    Aug 13, 2007
    Messages:
    70
    Likes Received:
    0
    I'm cross-posting this here; I hope the mods don't mind:

    Okay, I got the tunnel up and working with the latest version of 3cx. I'm using a VOIP client build I downloaded today. Using the tunnel, I can connect to the 3cx server from a remote location, and I can proxy the phone to it. Using the proxied hardphone through the tunnel, I can make calls and get two-way audio without any problem. However, when I attempt to call TO the proxied phone, I end up being able to receive audio on the proxied phone (but cannot transmit audio); the phone is stuck on "answering," and after the SIP response timout (in my case, ~30 seconds), the connection hangs up.

    I did a wireshark packet inspection, and there was tons of garbage data moving from the SIP tunnel to the computer proxy. Here's a sample:
    Unknown request: \355\002\022\375Sip0ACK sip:407@192.168.1.100:5060

    Here's what the verbose server logs look like when I make a call to that extension:
    21:38:38.252 MediaServerReporting::RTPReceiver [MS105000] C:50.3: No RTP packets were received:remoteAddr=127.0.0.1:10248,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7110
    21:38:38.252 Call::Terminate [CM503008]: Call(50): Call is terminated
    21:38:38.252 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:38.190 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:38.174 Call::Terminate [CM503008]: Call(50): Call is terminated
    21:38:38.174 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:22.455 MediaServerReporting::SetRemoteParty [MS210001] C:49.1:Answer received. RTP connection: 192.168.0.1:16528(16529)
    21:38:22.455 CallLeg::setRemoteSdp Remote SDP is set for legC:50.5
    21:38:22.455 Call::Terminate [CM503008]: Call(49): Call is terminated
    21:38:22.346 MediaServerReporting::SetRemoteParty [MS210002] C:49.1:Offer provided. Connection(transcoding mode): 192.168.0.12:9014(9015)
    21:38:22.346 Call::Terminate [CM503008]: Call(49): Call is terminated
    21:38:22.346 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:22.252 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:22.237 CallLeg::eek:nRefer Relpaces: MTZjNzg4ZjlmMjhiODNmYzIyMGQ1MWYzM2FlODE1ZWQ.;to-tag=80026279;from-tag=5e1a105e
    21:38:22.237 CallLeg::eek:nRefer Refer: from="CROMPTON,RYAN"[sip:8013181491@127.0.0.1:5060];tag=984ffc36; to=[sip:407@127.0.0.1:5060];tag=680d784c; RefTo="CROMPTON,RYAN"[sip:8013181491@127.0.0.1:5060?Replaces=MTZjNzg4ZjlmMjhiODNmYzIyMGQ1MWYzM2FlODE1ZWQ.%3Bto-tag%3D80026279%3Bfrom-tag%3D5e1a105e];tag=80026279
    21:38:22.237 CallLeg::eek:nConfirmed Session 27780 of leg C:50.1 is confirmed
    21:38:22.096 CallCtrl::eek:nLegConnected [CM503007]: Call(50): Device joined: sip:407@192.168.1.100:5060
    21:38:22.018 MediaServerReporting::SetRemoteParty [MS210001] C:50.3:Answer received. RTP connection: 127.0.0.1:10248(10249)
    21:38:22.018 Extension::printEndpointInfo [CM505001]: Ext.407: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-5.2.8] Transport: [sip:192.168.0.12:5060]
    21:38:22.018 CallLeg::setRemoteSdp Remote SDP is set for legC:50.3
    21:38:22.018 CallCtrl::eek:nAnsweredCall [CM503002]: Call(50): Alerting sip:407@192.168.1.100:5060
    21:38:19.330 Extension::printEndpointInfo [CM505001]: Ext.407: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX_VoIP_Client] Transport: [sip:192.168.0.12:5060]
    21:38:19.330 CallCtrl::eek:nAnsweredCall [CM503002]: Call(50): Alerting sip:407@127.0.0.1:5070;rinstance=1b0fa01881287341
    21:38:18.737 MediaServerReporting::SetRemoteParty [MS210002] C:50.4:Offer provided. Connection(transcoding mode): 127.0.0.1:7112(7113)
    21:38:18.674 MediaServerReporting::SetRemoteParty [MS210002] C:50.3:Offer provided. Connection(transcoding mode): 127.0.0.1:7110(7111)
    21:38:18.643 MediaServerReporting::SetRemoteParty [MS210002] C:50.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7108(7109)
    21:38:18.596 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(50): Calling: Shared:Ext.407@[Dev:sip:407@127.0.0.1:5070;rinstance=1b0fa01881287341, Dev:sip:407@192.168.1.100:5060, Dev:sip:407@192.168.1.115:5060]
    21:38:18.596 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:407@127.0.0.1:5060]
    21:38:18.471 CallCtrl::eek:nIncomingCall [CM503001]: Call(50): Incoming call from Ext.302 to [sip:407@127.0.0.1:5060]
    21:38:18.471 CallLeg::eek:nNewCall [CM500002]: Info on incoming INVITE:
    INVITE sip:407@127.0.0.1:5060 SIP/2.0
    Via: SIP/2.0/UDP 127.0.0.1:40600;branch=z9hG4bK-d8754z-b17a6765950bae62-1---d8754z-;rport=40600
    Max-Forwards: 70
    Contact: [sip:302@127.0.0.1:40600]
    To: [sip:407@127.0.0.1:5060]
    From: "CROMPTON,RYAN"[sip:8013181491@127.0.0.1:5060];tag=984ffc36
    Call-ID: ZDQxZTM4Mzk2YTMyY2I0MmRkODA1OGE3ZmM3MWE3NzI.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Proxy-Authorization: Digest username="302",realm="3CXPhoneSystem",nonce="12859011497:6f64201d1935f631f632e9d3c0bb5835",uri="sip:407@127.0.0.1:5060",response="0dfa1e16f0ce58d01400d7a79af39739",algorithm=MD5
    Supported: replaces
    User-Agent: 3CX IVR
    Content-Length: 0


    21:38:07.580 CallLeg::eek:nConfirmed Session 27740 of leg C:49.1 is confirmed
    21:38:07.487 CallCtrl::eek:nLegConnected [CM503007]: Call(49): Device joined: sip:302@127.0.0.1:40600;rinstance=2030f222e60fbc25
    21:38:07.487 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:07.424 CallCtrl::eek:nLegConnected [CM503007]: Call(49): Device joined: sip:8012247199@192.168.0.1:5060
    21:38:07.424 MediaServerReporting::SetRemoteParty [MS210005] C:49.1:Answer provided. Connection(proxy mode):192.168.0.12:9014(9015)
    21:38:07.424 MediaServerReporting::SetRemoteParty [MS210001] C:49.2:Answer received. RTP connection: 127.0.0.1:40610(40611)
    21:38:07.424 CallLeg::setRemoteSdp Remote SDP is set for legC:49.2
    21:38:07.424 Extension::printEndpointInfo [CM505001]: Ext.302: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] Transport: [sip:127.0.0.1:5060]
    21:38:07.424 CallCtrl::eek:nAnsweredCall [CM503002]: Call(49): Alerting sip:302@127.0.0.1:40600;rinstance=2030f222e60fbc25
    21:38:06.955 MediaServerReporting::SetRemoteParty [MS210004] C:49.2:Offer provided. Connection(proxy mode): 127.0.0.1:7106(7107)
    21:38:06.924 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(49): Calling: Ext:Ext.302@[Dev:sip:302@127.0.0.1:40600;rinstance=2030f222e60fbc25]
    21:38:06.924 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:302@64.50.120.38:5060]
    21:38:06.924 MediaServerReporting::SetRemoteParty [MS210000] C:49.1:Offer received. RTP connection: 192.168.0.1:16528(16529)
    21:38:06.924 CallLeg::setRemoteSdp Remote SDP is set for legC:49.1
    21:38:06.924 Line::printEndpointInfo [CM505003]: Provider:[Veracity] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.0.12:5060]
    21:38:06.924 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302
    21:38:06.705 CallCtrl::eek:nIncomingCall [CM503001]: Call(49): Incoming call from 8013181491@(Ln.10019@Veracity) to [sip:302@64.50.120.38:5060]
    21:38:06.705 MediaServerReporting::STUN [MS101003] C:49.1: Possible firewall problem. Address mapping failed on STUN server 192.168.0.12:3478 for local address ":9014"
    21:38:00.549 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10019 forwards to DN:302


    Any ideas?

    Other notes: I'm using a SPA-922 as my hardphone. I also tried this with a GRandstream Budgetone, and both exhibited the same behavior. One thing I did have to do with both, however, was set the proxy IP to computer proxy IP port 5080. If I didn't do this, the phones wouldn't register at all.

    Recap: Proxied phone can make calls. When calls are made TO proxied phone, phone rings, I can pick up receiver, but phone only displays "Answering" until SIP timeout is reached, and session is terminated.

    I'll closs-post this in a couple places, but let me know what you guys need... I'm eager to get our telecommuting solution available, specially with gas prices being what they are!
    -Ryan
     
  2. darrellchapman

    Joined:
    Nov 26, 2007
    Messages:
    268
    Likes Received:
    0
    If you must cross post, please provide a link in your second post so that people can click on it and see if it's been replied to.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. romvex

    Joined:
    Dec 8, 2007
    Messages:
    3
    Likes Received:
    0
    Did you get any solution on this?
    I have the same problem. More, once, it worked both ways: call to and from the proxied hardphone. I don't know how but the server received answer on rtp connection from the hardphone. Only for two calls then the regular state came into place again: no calls can be made to tunneled hardphone as described in this forum.
     
  4. tein

    Joined:
    Jan 21, 2008
    Messages:
    5
    Likes Received:
    0
    Same problem here with the Linksys SPAs. Even with 3CX Tech. Support we have not found the solution for this problem and we were struggling for a couple of days with this issue. Eventualy we have to drop out this case. So if anybody founds out the solution for this problem, he will be the hero of the day. Regards, g
     
Thread Status:
Not open for further replies.