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.

3CX with SideWinder's SIP Proxy

Discussion in '3CX Phone System - General' started by brightidea, Jun 3, 2008.

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

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Hi.

    I have discovered a bug in the system's uri parser: if the request contains semicolon's it simply fails. This situation is causing the software to block any incoming call through SideWinder (Secure Computing) firewall because its sip proxy keeps adding the x-swhost tag to the caller's address for all natted requests.

    example:
    INVITE sip:1234567@192.168.10.12:53848;x-swhost=11.11.22.33 SIP/2.0
    would fail, wheras
    INVITE sip:1234567@192.168.10.12:53848 SIP/2.0
    will not

    Thanks for your support.
     
  2. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    Logs?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. brightidea

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    The following is taken from log:

    INVITE sip:66567461425@192.168.10.12:13646;x-swhost=77.110.81.1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.12:13646;branch=548e5f6e247c9570
    Max-Forwards: 70
    Contact: <sip:341@192.168.10.12:13646;transport=udp;x-swhost=72.20.112.114;x-swport=5060>
    To: "66567461425"<sip:66567461425@192.168.10.12:13646;x-swhost=77.110.81.1>
    From: "341"<sip:341@192.168.10.12:13646;x-swhost=77.110.81.1>;tag=1478176014
    Call-ID: SIPCALL-2025395521-431757423@192.168.10.12
    CSeq: 1 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
    Supported: ICE
    User-Agent: GTalk2VoIP V7 by RZ and UGIN, Tyumen, Russia
    Content-Length: 0

    <br>
    13:17:58.190|.\Line.cpp(331)|Log2||LineCfg::getInboundTarget:[CM503011]: Inbound office hours' rule for LN:20000 forwards to DN:<br>
    13:17:58.549|.\CallCtrl.cpp(100)|Log2||CallCtrl::eek:nIncomingCall:[CM503001]: Call(1): Incoming call from 341@(Ln.20000@outside) to <sip:192.168.10.56:5060><br>
     
  4. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    There's no problem with parsing headers. At least I do not see any in logs. But what I see is incorrect inbound rule which points to nowhere: "...rule for LN:20000 forwards to DN:"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. brightidea

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    If it had recognized the phone number from the uri then why have it taken that path of trying to route the call it to another phone number while that option is actually turned off as I have selected 'end call' for the route of incoming calls from the voip provider (gtalk2voip / ln.30000).

    The following should make the picture clearer to you - I hope

    14:19:46.381 Call::Terminate [CM503008]: Call(27): Call is terminated
    14:19:46.381 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:30000 forwards to DN:
    14:19:46.365 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:30000 forwards to DN:
    14:19:46.365 Call::RouteFailed [CM503014]: Call(27): Attempt to reach [sip:192.168.10.56:5060] failed. Reason: Not Found
    14:19:46.365 CallCtrl::eek:nSelectRouteReq [CM503013]: Call(27): No known route to target: [sip:192.168.10.56:5060]
    14:19:46.365 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:192.168.10.56:5060]
    14:19:46.365 MediaServerReporting::SetRemoteParty [MS210000] C:27.1:Offer received. RTP connection: 192.168.10.12:4008(4009)
    14:19:46.365 CallLeg::setRemoteSdp Remote SDP is set for legC:27.1
    14:19:46.365 Line::printEndpointInfo [CM505003]: Provider:[gtalk] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [GTalk2VoIP V7 by RZ and UGIN, Tyumen, Russia] Transport: [sip:192.168.10.56:5060]
    14:19:46.365 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:30000 forwards to DN:
    14:19:46.350 CallCtrl::eek:nIncomingCall [CM503001]: Call(27): Incoming call from brightidea_at_gmail.com@(Ln.30000@gtalk) to [sip:192.168.10.56:5060]
    14:19:46.350 MediaServerReporting::STUN [MS101003] C:27.1: Possible firewall problem. Address mapping failed on STUN server 192.168.10.56:3478 for local address ":9004"
    14:19:46.256 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:30000 forwards to DN:
    14:19:46.240 CallLeg::eek:nNewCall [CM500002]: Info on incoming INVITE:
    INVITE sip:241@192.168.10.56:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.12:38913;branch=75237bcd6eeea8c0
    Max-Forwards: 70
    Contact: [sip:brightidea_at_gmail.com@192.168.10.12:38913;transport=udp;x-swhost=72.20.112.114;x-swport=5060]
    To: "241"[sip:241@192.168.10.56:5060]
    From: "brightidea_at_gmail.com"[sip:brightidea_at_gmail.com@gtalk.gtalk2voip.com];tag=1893647486
    Call-ID: SIPCALL-477513299-01302521@192.168.10.12
    CSeq: 1 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
    Supported: ICE
    User-Agent: GTalk2VoIP V7 by RZ and UGIN, Tyumen, Russia
    Content-Length: 0
     
  6. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    Incoming calls from external lines are routed according to inbound rules ONLY and not content of request line. You have set inbound rule to end call - and it terminates the call. What is the problem then?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. brightidea

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Re: 3CX with SideWinder's SIP Proxy - Bug

    Thank you Archie. I cleared my settings and did them again and then restarted the server. Only then it worked like I'd expected.

    I believe that I need to restart the server everytime I make major changes in the settings.
     
Thread Status:
Not open for further replies.