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.
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.
Comment