Genesys Engage on-premises

 View Only

Discussion Thread View

  • 1.  SIP-Proxy and SIP-Server

    Posted 06-30-2020 00:06
    Hi, 
    When sip-proxy send options message to sip-server,
    proxy send only ip address.
    as result, sip-server doesnt know name of sip-proxy and some error message occured.
    how to resolve it?

    in sip-server logs,

    13:02:33.431: SIPTR: Received [0,UDP] 373 bytes from 172.168.20.133:5060 <<<<<
    OPTIONS sip:172.168.20.131:5060 SIP/2.0
    From: <sip:172.168.20.133:5060>;tag=006BF788-B5C2-1EFA-B26C-8514A8ACAA77-184
    To: <sip:172.168.20.131:5060>
    Call-ID: 006BF77E-B5C2-1EFA-B26C-8514A8ACAA77-184@hmproxy1.hmc.com
    CSeq: 1593489753 OPTIONS
    Content-Length: 0
    Via: SIP/2.0/UDP hmproxy1.hmc.com:5060;branch=z9hG4bK003FF354-B959-1EFA-B26C-8514A8ACAA77
    Max-Forwards: 0

    13:02:33.431: Unable to resolve number for DN:Anonymous
    13:02:33.431: trunk ip addr hmproxy1.hmc.com
    13:02:33.431 Std 52002 Gateway for address 'hmproxy1.hmc.com', number 'Anonymous' is not found.
    13:02:33.431: Unknown Gateway Reject Code 0 ignored

    #SIP/VolP

    ------------------------------
    Chulmin Park
    I4WAY Co., Ltd.
    ------------------------------


  • 2.  RE: SIP-Proxy and SIP-Server

    Posted 07-01-2020 06:07
    We're only using SIP Proxy in a lab environment (IP Takeover otherwise), but I've witnessed this myself.  Because it's just a lab environment, I've gone with the enable-unknown-gateway option, but I imagine it would be better to go with the Fake Trunk normally.  Note, I dont think this should be causing you issues except making your logging messy and large.  Not sure if theres a better solution these days.

    • F5 Load balancer sends SIP OPTIONS messages to SIP Server HA pair to monitor which of the nodes is active. The SIP Server which responds on the OPTIONS message is marked by F5 as an active node and considered as Primary
    • Message "Gateway for address 'zzz.example.com', number 'anonymous' is not found" is produced if SIP Server cannot resolve the Trunk DN where the message is sent from
    Solution
    • Configure SIP Server to accept SIP requests from gateways which are not represented as a TrunkDNs
    enable-unknown-gateway = true
    • Create a fake TrunkDN for F5 load balancer with a prefix which guarantees that no calls to be sent to this trunk. Set the following options in the annex tab:
    contact = <sip:[IP_Address or FQDN of F5 Load balancer]>
    prefix = "Fake_Prefix"
    • Configure SIP Server not to produce messages if it is unable to find the Trunk DN. To do it edit the .lms file which is located in the directory where SIP Server is installed, and remove the following string:

    52002|STANDARD|GCTI_UNKNOWN_GATEWAY|Gateway for address '%s', number '%s' is not found.


    ------------------------------
    Jason McLennan
    Commonwealth Bank of Australia
    ------------------------------

    Original Message


  • 3.  RE: SIP-Proxy and SIP-Server

    Posted 07-02-2020 19:32
    Thank you for your response.
    All three options look good.
    It is difficult to enable an unknown gateway for security reasons.
    The best thing I think, is to have the option of setting up a trusted IP.

    ------------------------------
    Chulmin Park
    I4WAY Co., Ltd.
    ------------------------------

    Original Message


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources