1. Brekeke Product Name and Version:3.8
2. Java version:1.8
3. OS type and the version:RHEL6
4. UA (phone), gateway or other hardware/software involved:
5. Your problem:
My following rule runs good without $webget/$log.
My all requests does not match the rule as soon as I add the $webget/$log lines. what is wrong with my rule, id $webget available in Adv version only?
Matching Patterns
$addr = ^10\.1\.1\.1
From = sip:(.+)@
$request = sip:123(.+)@
$header("X-custom1")= (.+)
$header("X-custom2")= (.+)
$header("X-custom3")= (.+)
$webget("http://192.168.2.2/test.php?test=%2") = (.+)
Deploy Patterns
From = sip:%1@10.2.2.2
To = sip:%2@%10.10.10.10
$b2bua = false
$rtp = false
X-custom1 = %3
X-custom2 = %4
X-custom3 = %5
$log = %6
WebGet failing
Moderator: Brekeke Support Team
> $webget available in Adv version only?
Yes.
http://wiki.brekeke.com/wiki/DialPlan-Matching-webGet
>> Note: $webget method is available in the Advanced Edition only.
Anyway... you don't have to put X-custom headers manually because they will be kept in an outgoing SIP packets.
So your dial plan rule will be like this.
[Matching Patterns]
$request = ^INVITE
$addr = ^10\.1\.1\.1
From = sip:(.+)@
$request = sip:123(.+)@
$webget("http://192.168.2.2/test.php?test=%2") = (.+)
[Deploy Patterns]
From = sip:%1@10.2.2.2
To = sip:%2@%10.10.10.10
$b2bua = false
$rtp = false
$log = %3
Yes.
http://wiki.brekeke.com/wiki/DialPlan-Matching-webGet
>> Note: $webget method is available in the Advanced Edition only.
Anyway... you don't have to put X-custom headers manually because they will be kept in an outgoing SIP packets.
So your dial plan rule will be like this.
[Matching Patterns]
$request = ^INVITE
$addr = ^10\.1\.1\.1
From = sip:(.+)@
$request = sip:123(.+)@
$webget("http://192.168.2.2/test.php?test=%2") = (.+)
[Deploy Patterns]
From = sip:%1@10.2.2.2
To = sip:%2@%10.10.10.10
$b2bua = false
$rtp = false
$log = %3