Question on SM can not use adaptation to convert SIP invite header

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • yingbinzhang
    Aspiring Member
    .
    • Mar 2010
    • 2
    #1

    Question on SM can not use adaptation to convert SIP invite header

    Hi,

    I configured an adaptation with module name "DigitConversionAdapter" to convert the destination IP feild of SIP invite header sent from Dialogic, two parameters are added also.

    Module name: DigitConversionAdapter
    Module parameters: iodstd=aura.ctrip.com iosrcd=aura.ctrip.com
    Matching Pattern 81070000
    Min=8
    Max=8
    Delete=8
    Insert=27100 which is extension number.

    The problem is dialogic sent sip invite like "called#@SM-100 IP", to SM. Using adaptation, the SM-100_IP should be changed to SIP domain name which already defined in this adaptation, but failed, SM will NOT use this adaptation to convert the SM-100_IP. But, if I change the SM-100 IP to any other IP, such as IP of default gateway, the same adaptation will work, change the default gateway's IP to "aura.ctrip.com", and then route the call sucessfully.

    My question is why SM does NOT use adaptation to convert the SM-100 IP address within SIP invite header, but can convert any others.
    Tags: None
  • yingbinzhang
    Aspiring Member
    .
    • Mar 2010
    • 2
    #2
    Below is for the failed call routing
    ************************************************** *********************
    2010-03-12 23:36:13,702 datadistributionlayer.JGroupReceiverAdapter FINEST - handle(): src: 10.255.189.21:39095, message=DataDistLayerMessage[host=DataDistLayerMemberAddr[memberName='null', clusterName='10.255.189.21', hostId='10.255.189.21:34413'], targetApp=ASM_CALL_PROC_SERVLET, messageType=0, payload=sip:[email protected] : sip:[email protected] : 10.255.188.91 : 5060 : UDP : 1268408222974]
    2010-03-12 23:36:13,702 common.ASMCallProcessingServlet FINEST - testCallRouting got a request with input sip:[email protected] : sip:[email protected] : 10.255.188.91 : 5060 : UDP : 1268408222974
    2010-03-12 23:36:13,702 common.ASMCallProcessingServlet FINEST - Application Session 016asm-callprocessing.sar347930378~1268408173702~-1744061638~1 was created
    2010-03-12 23:36:13,703 common.ASMCallProcessingServlet FINEST - Session with call ID [email protected] and id 016asm-callprocessing.sar347930378~1268408173703~-1744061637~1 was created.
    2010-03-12 23:36:13,703 common.ASMCallProcessingServlet FINEST - INVITE([email protected]): SMCallProcessing doRequest SAS 016asm-callprocessing.sar347930378~1268408173702~-1744061638~1
    2010-03-12 23:36:13,703 common.ASMCallProcessingServlet FINEST - INVITE([email protected]): SS 016asm-callprocessing.sar347930378~1268408173703~-1744061637~1
    2010-03-12 23:36:13,703 common.ASMCallProcessingServlet FINEST - set ROUTING_APPSESSION in request
    2010-03-12 23:36:13,703 siproutingelement.SREUtilities FINEST - INVITE([email protected]): getOriginatingEntity using parameters: 10.255.188.91 5060 UDP
    2010-03-12 23:36:13,703 dao.SIPEntityDAO FINEST - getSIPEntityByAddress(10.255.188.91) returned [SipEntity[id=65558, name="nt-dialogic-south-01", type=Gateway, addr=10.255.188.91, 3263=false, adapt=32771, proxy=null, loc=null, mon=true/100/100, cdr=none]]
    2010-03-12 23:36:13,704 dao.HostNameDAO FINEST - getResolvedNameByAddress(10.255.188.91) returned []
    2010-03-12 23:36:13,704 datamgr.SipRoutingElementDM FINEST - getOriginatingEntity(10.255.188.91) matched link Link[entityId1=65537, entityId2=65558, portEntity1=5060, portEntity2=5060, trusted=true, transport=UDP, biDirId=null]; returning entity SipEntity[id=65558, name="nt-dialogic-south-01", type=Gateway, addr=10.255.188.91, 3263=false, adapt=32771, proxy=null, loc=null, mon=true/100/100, cdr=none]
    2010-03-12 23:36:13,704 siproutingelement.SREUtilities FINEST - INVITE([email protected]): getOriginatingEntity returned entity with id = 65558
    2010-03-12 23:36:13,704 siproutingelement.SREUtilities FINEST - INVITE([email protected]): remote host is trusted
    2010-03-12 23:36:13,704 datamgr.NameResolutionDM FINEST - matchHosts(10.255.188.21,10.255.188.21) returning true
    2010-03-12 23:36:13,704 common.ASMCallProcessingServlet FINE - INVITE([email protected]): No domain was found for sip:[email protected]; returning SC_NOT_FOUND
    class com.avaya.asm.core.exceptions.DMException: No listen port entry for request sent to local instance for port 5060 on UDP.






    Below is for the sucess call routing
    ************************************************** *********************
    2010-03-12 23:36:20,531 datadistributionlayer.JGroupReceiverAdapter FINEST - handle(): src: 10.255.189.21:39095, message=DataDistLayerMessage[host=DataDistLayerMemberAddr[memberName='null', clusterName='10.255.189.21', hostId='10.255.189.21:34413'], targetApp=ASM_CALL_PROC_SERVLET, messageType=0, payload=sip:[email protected] : sip:[email protected] : 10.255.188.91 : 5060 : UDP : 1268408229808]
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - testCallRouting got a request with input sip:[email protected] : sip:[email protected] : 10.255.188.91 : 5060 : UDP : 1268408229808
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - Application Session 016asm-callprocessing.sar347930378~1268408180531~-1744061626~1 was created
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - Session with call ID [email protected] and id 016asm-callprocessing.sar347930378~1268408180531~-1744061625~1 was created.
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - INVITE([email protected]): SMCallProcessing doRequest SAS 016asm-callprocessing.sar347930378~1268408180531~-1744061626~1
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - INVITE([email protected]): SS 016asm-callprocessing.sar347930378~1268408180531~-1744061625~1
    2010-03-12 23:36:20,531 common.ASMCallProcessingServlet FINEST - set ROUTING_APPSESSION in request
    2010-03-12 23:36:20,531 siproutingelement.SREUtilities FINEST - INVITE([email protected]): getOriginatingEntity using parameters: 10.255.188.91 5060 UDP
    2010-03-12 23:36:20,532 dao.SIPEntityDAO FINEST - getSIPEntityByAddress(10.255.188.91) returned [SipEntity[id=65558, name="nt-dialogic-south-01", type=Gateway, addr=10.255.188.91, 3263=false, adapt=32771, proxy=null, loc=null, mon=true/100/100, cdr=none]]
    2010-03-12 23:36:20,532 dao.HostNameDAO FINEST - getResolvedNameByAddress(10.255.188.91) returned []
    2010-03-12 23:36:20,532 datamgr.SipRoutingElementDM FINEST - getOriginatingEntity(10.255.188.91) matched link Link[entityId1=65537, entityId2=65558, portEntity1=5060, portEntity2=5060, trusted=true, transport=UDP, biDirId=null]; returning entity SipEntity[id=65558, name="nt-dialogic-south-01", type=Gateway, addr=10.255.188.91, 3263=false, adapt=32771, proxy=null, loc=null, mon=true/100/100, cdr=none]
    2010-03-12 23:36:20,532 siproutingelement.SREUtilities FINEST - INVITE([email protected]): getOriginatingEntity returned entity with id = 65558
    2010-03-12 23:36:20,532 siproutingelement.SREUtilities FINEST - INVITE([email protected]): remote host is trusted
    2010-03-12 23:36:20,532 datamgr.NameResolutionDM FINEST - matchHosts(10.255.188.21,10.255.188.2) returning false
    2010-03-12 23:36:20,532 common.AsmUtilities FINEST - CallRoutingTest Output: Checking NRP to determine if this is a call to an emergency number.



    The diffrerence is:
    **********************************

    2010-03-12 23:36:13,704 datamgr.NameResolutionDM FINEST - matchHosts(10.255.188.21,10.255.188.21) returning true


    2010-03-12 23:36:20,532 datamgr.NameResolutionDM FINEST - matchHosts(10.255.188.21,10.255.188.2) returning false




    Please note 10.255.188.21 is the SM100 IP, and 10.255.188.2 is dummy IP.

    Comment

    Previous template Next
    Loading