Have you pushed the [Apply Rules] button after you modified the DialPlan? Yes, I have. And from the history page, I can see the Rule has already taken effect, but on "INVITE" requests. My sessions were modified through "UPDATE" in-dialog and the rule just did not impact them. There is no other ...

Are INVITE and UPDATE using a same Call-ID? Yes. Same Call-ID. I donot know how to attach a file to this thread and I can figoure out that: 1. If the server's IP is 192.168.6.xxx, and the UAs' IP are 192.168.0.xxx which are behind a Router that is at the same subnet as the SIP server, say the SIP ...

Are you sure the above DialPlan rule is executed? It seems $rtp=false is not called. Check it at the DialPlan History page. > c=117.22.xx.xx Is it the caller side's global IP address? Or is it the SIP Server's IP address? From the DialPlan History, the above was executed on "INVITE" request, but ...

Is it an UPDATE sent within an INVITE's dialog? If so, set $request = ^INVITE. Yes. The original "UPDATE" request contains c=192.168.0.108 and the forwarded "UPDATE" contains c=117.22.xx.xx That's what I am confused. There is only one dialplan. The "Match Pattern" is : $request = ^INVITE and the ...

Laurie wrote:Add $rtp=off in the DialPlan's DeployPattern.
It disables RTP-relay even if the SIP Server detects NAT.

How should I set the "Matching Patterns"? I just left it empty and it just did not work. I could not set "$request" to "^UPDATE". Thanks.

1. Brekeke Product Name and Version: Brekeke SIP Server, Version 3.5.2.8, Evaluation 2. Java version: 1.7.0_65 (OpenJDK 64-Bit Server VM) 3. OS type and the version: CentOS Linux release 6.0 (Final) Linux 2.6.32-279.14.1.el6.x86_64 4. UA (phone), gateway or other hardware/software involved: PJSIP 5 ...

Hi taitan, thank you for the reply. > Are there any provisional response (such as 180) to re-INVITE from another UA? If so, you can send CANCEL to the re-INVITE. Yes, I let the other peer send a "180 Ringing" to the re-INVITE request, and the SIP server just respond with a "481 Call Leg/Transaction ...

1. Brekeke Product Name and Version: Brekeke SIP Server, Version 3.4.7.0, Evaluation 2. Java version: java version "1.7.0_91" OpenJDK Runtime Environment (IcedTea 2.6.2) (Arch Linux build 7.u91_2.6.2-1-i686) OpenJDK Client VM (build 24.91-b01, mixed mode) 3. OS type and the version: Linux ...