| Author |
Message |
 Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
 Forum: Brekeke SIP Server Forum Posted: Thu Jun 18, 2015 12:05 pm Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
| 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 ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Thu Jun 18, 2015 11:01 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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** ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Thu Jun 18, 2015 4:34 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
| 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 ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Wed Jun 17, 2015 1:13 pm Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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:U ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Wed Jun 17, 2015 10:43 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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 NOTI ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Wed Jun 17, 2015 5:35 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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 ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Sat May 30, 2015 3:44 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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 cap ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Fri May 29, 2015 5:31 pm Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
Are there any response sent from the Brekeke SIP Server to NOTIFY?
You can check the error response code in the
There is no response at all sent from BSS
There are no errors present in the lo ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Fri May 29, 2015 1:18 pm Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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 ... |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Fri May 29, 2015 1:11 pm Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
| There would be no SUBSCRIBE related to this NOTIFY as it is generated on the PBX as means to prompt the phone to reboot. |
| Topic: SIP NOTIFY (Event: check-sync) not relaying to UA |
cphillips.ia
Replies: 21
Views: 19480
|
Forum: Brekeke SIP Server Forum Posted: Fri May 29, 2015 10:37 am Subject: SIP NOTIFY (Event: check-sync) not relaying to UA |
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/sof ... |
| Topic: Filtering Policy reliad from CLI |
cphillips.ia
Replies: 4
Views: 6182
|
Forum: Brekeke SIP Server Forum Posted: Tue Apr 21, 2015 2:40 pm Subject: Filtering Policy reliad from CLI |
| That was simple enough... Thanks! |
| Topic: Filtering Policy reliad from CLI |
cphillips.ia
Replies: 4
Views: 6182
|
Forum: Brekeke SIP Server Forum Posted: Tue Apr 21, 2015 2:17 pm Subject: Filtering Policy reliad from CLI |
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 ... |
| Topic: Filtering Policy reliad from CLI |
cphillips.ia
Replies: 4
Views: 6182
|
Forum: Brekeke SIP Server Forum Posted: Tue Apr 21, 2015 12:30 pm Subject: Filtering Policy reliad from CLI |
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), gatewa ... |
| Topic: RFC3326 (Reason header) pass thru on CANCEL |
cphillips.ia
Replies: 2
Views: 3423
|
Forum: Brekeke SIP Server Forum Posted: Tue Apr 07, 2015 1:50 pm Subject: RFC3326 (Reason header) pass thru on CANCEL |
| Excellent, thank you. |
| Topic: RFC3326 (Reason header) pass thru on CANCEL |
cphillips.ia
Replies: 2
Views: 3423
|
Forum: Brekeke SIP Server Forum Posted: Tue Apr 07, 2015 6:12 am Subject: RFC3326 (Reason header) pass thru on CANCEL |
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 o ... |
| Topic: Multiple Domain Questions / Confusion |
cphillips.ia
Replies: 8
Views: 6427
|
Forum: Brekeke SIP Server Forum Posted: Fri Nov 21, 2014 10:12 am Subject: Multiple Domain Questions / Confusion |
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 Patter ... |
| Topic: Multiple Domain Questions / Confusion |
cphillips.ia
Replies: 8
Views: 6427
|
Forum: Brekeke SIP Server Forum Posted: Thu Nov 20, 2014 6:55 am Subject: Multiple Domain Questions / Confusion |
| 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 ... |
| Topic: Multiple Domain Questions / Confusion |
cphillips.ia
Replies: 8
Views: 6427
|
Forum: Brekeke SIP Server Forum Posted: Wed Nov 19, 2014 6:45 am Subject: Multiple Domain Questions / Confusion |
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.co ... |
| Topic: Multiple Domain Questions / Confusion |
cphillips.ia
Replies: 8
Views: 6427
|
Forum: Brekeke SIP Server Forum Posted: Tue Nov 18, 2014 2:50 pm Subject: Multiple Domain Questions / Confusion |
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 Ast ... |
| Topic: Multiple Domain Questions / Confusion |
cphillips.ia
Replies: 8
Views: 6427
|
Forum: Brekeke SIP Server Forum Posted: Tue Nov 18, 2014 10:12 am Subject: Multiple Domain Questions / Confusion |
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/so ... |
| |
