I meant that in the example of my last reply (a NOTIFY for MWI), PBX sends a NOTIFY to BSS and then BSS relays it on (with an added via and record route) to the Endpoint UA (Polycom phone) and the MWI lights up. I included both packets for verification (packet from PBX to BSS then BSS to Endpoint ...

Actual from port is 5060 Sender of NOTIFY is an Asterisk PBX Here is a NOTIFY packet from a MWI trigger (which works perfectly and passes through without issue): NOTIFY sip:120@**BSSADDRESS**:5060 SIP/2.0 Via: SIP/2.0/UDP **PBXADDRESS**:5060;branch=z9hG4bK6b47c993;rport Max-Forwards: 70 From ...

That is what the packet looks to be indicating as the From address, but being a check-sync Event there is no reply required from the UA, only a timestamp check of autoprovisioning configuration files against the PBX (via FTP or TFTP in this case). I should also mention that this was captured via a ...

I sure will. Thanks for the reply! NOTIFY sip:120@**BSSADDRESS**:5060 SIP/2.0 Via: SIP/2.0/UDP **PBXADDRESS**:0;branch=z9hG4bK60fe2fe2;rport Max-Forwards: 70 From: "Unknown" <sip:Unknown@**PBXADDRESS**:0>;tag=as2d46885b To: <sip:120@**BSSADDRESS**:5060> Contact: <sip:Unknown@**PBXADDRESS**:0> Call ...

The log setting "net.listener.loglevel.file=255" will write all of received SIP packets into the log file... Is the SIP server running on the port 5060? Does the sender client send NOTIFY to the port 5060? Which transport is it ? UDP? or TCP? Yes, all of the packets are there in the log except the ...

Sorry for the slow reply, this had to go on the back burner for a bit... I set log levels to 255 as described in the Wiki article (which is extremely verbose), but there appears to be no record of the NOTIFY packets in the log. This is strange since the packets are definitely making it there as they ...

It is strange.. Did you capture packets to confirm that NOTIFY reaches the SIP server? Enable the logging. It may provide a clue. http://wiki.brekeke.com/wiki/log-SIP-packets Yes, I am capturing the packets @ the BSS server. Would logging the SIP packet with BSS provide any more info than tcpdump ...

Are there any response sent from the Brekeke SIP Server to NOTIFY? You can check the error response code in the [Error Logs] page after you set "INVITE Only=off". Can you find NOTIFY sender's IP address (PBX's IP address) under the [Blocked IP Address] list? There is no response at all sent from ...

Quick Update...

Looking at the PBX logs, Asterisk seems to think BSS does not support NOTIFY at all

[2015-05-29 16:15:51] WARNING[663]: chan_sip.c:20568 handle_response: Host 'x.x.x.x:5060' does not implement 'NOTIFY'

There would be no SUBSCRIBE related to this NOTIFY as it is generated on the PBX as means to prompt the phone to reboot.

1. Brekeke Product Name and Version: Brekeke SIP Server 3.4.5.1/410 2. Java version: 1.6.0_32 3. OS type and the version: Debian Wheezy 64bit 4. UA (phone), gateway or other hardware/software involved: Polycom Phones, Asterisk PBX 5. Your problem: SIP NOTIFY Event: check-sync packets issued from PBX ...

That was simple enough... Thanks!

For example, we reload the dialplan after updating dialplan.tbl with:

java -classpath /var/lib/tomcat7/webapps/sip/WEB-INF/lib/ondosip.jar svctl localhost update rule

I was just looking for the correct function to call to apply the filtering policies....

1. Brekeke Product Name and Version: Brekeke SIP Server - 3.3.8.1/379-7 2. Java version: OpenJDK 64-Bit Server VM 3. OS type and the version: Debian 7 - 3.2.0-4-amd64 4. UA (phone), gateway or other hardware/software involved: any / independent of UA 5. Your Problem: -- No Problem, just a question ...

Excellent, thank you.

1. Brekeke Product Name and Version: Brekeke SIP Server - 3.3.8.1/379-7 2. Java version: OpenJDK 64-Bit Server VM 3. OS type and the version: Debian 7 - 3.2.0-4-amd64 4. UA (phone), gateway or other hardware/software involved: any / independent of UA 5. Your problem: Brekeke SIP server not passing ...

Hey cphillips, It seems your current DialPlan catches all of SIP request (not only REGISTER). I think you need to have $request = ^REGISTER in the Matching Patterns like this. Matching Patterns: $request = ^REGISTER To = sip:(.+)@test1.xyz.com You are correct, it is configured with a request type ...

Sorted this out and wanted to post the resolution. It was a simple dial plan issue due to compound misconfigurations... I should also note that, in the end I did not even need to add the domains to the Domains list (since I am only using 1 IP/interface) just enabled multiple domains and let the dial ...

Are these FQDN (e.g. test1.xyz.com) assigned for the Brekeke SIP Server? I mean.. does the DNS record of the domain point the SIP Server's IP address (y.y.y.y)? Yes. test1.xyz.com, test2.xyz.com, etc all point to y.y.y.y (the BSS). From there they are routed via Dial Plan to use Upper Reg to the ...

Thanks for the reply! Do you mean REGISTER's Contact URI points x.x.x.x? Is it a PBX's IP address? Yes, in the Registered Clients page they show the Upper Registration IP address (i.e the Asterisk PBX's IP not the IP of SIP Server). Have you assign new IP address or FQDN to the SIP Server for ...

1. Brekeke Product Name and Version: Brekeke SIP Server 3.3.8.1/379-7 2. Java version: 1.6.0_32 3. OS type and the version: Debian Wheezy 64bit 4. UA (phone), gateway or other hardware/software involved: Polycom Phones, Asterisk PBX 5. Your problem: I am seeking to use SIP Server for Upper ...