Search results

690 XML tester3.a2es.uk is just the syntax for specifying the transfer destination. It means transfer to 690@tester3.a2es.uk I hope that makes sense.

Yes, sure. The anti-action is what gets processed if the condition is not matched. In the example I gave 662 is where I want the unwanted calls to go - this could be anything you like, a recording, an extension with DND enabled, or a phone with the ringer turned off, or just a pain hang up...

Avoid doing too much in the inbound route. The inbound route is processed in the public context so anything you do there can affect all the domains. The safest thing to do is create a destination in the dialplan manager and send the calls to it in the inbound route, just like you would...

Your python code looks fine. So the only "Event-Subclass" headers that you see in the CUSTOM events are for sofia. I don't understand what is going on because you should be seeing the call center Event-Subclass in the CUSTOM events if mod_callcenter is working correctly.

If your three domains are on the same box then is_local should work for you. Enable it in the dialplan, and then, for good measure, do a Flush Cache and a Reload XML. If it is still not working, set your log level to at least 'NOTICE' and follow a call in the logs. is_local logs activity at...

How are you listening ALL events?

Check out event="CUSTOM" subclass="callcenter::info"

It looks like you may have put your local IP address in the ACL, only your SIP providers should go in there.

Is_local only works if the inbound route (DID) is on the same PBX, it stops the call going out to your SIP provider and then back in again. You may find this thread helpful: https://www.pbxforums.com/threads/dialling-in-from-a-second-pbx.5554/#post-22056

I don't do country black/whitelisting, I don't believe it offers comprehensive protection, but it may help in certain circumstances. Some may argue that it could give people a false sense of security. I put the links up because Andrew was interested in doing it. The lists came from...

I'm not dropping them, this would be an example where you would accept Fiji and maybe drop everything else. If you wanted to drop Fiji then you would down load the drop rule set, that would have drop statements, it's just a convenience, it's the list of IPs that matter, do with them whatever...

I believe xtables provides some addons/functions for iptables that are not available in the kernel by default. I'm not convinced about the benefits of blocking countries by IP range. Anyone serious about hacking you will just get a VPN to the US. I have tunnels to several countries for...

Sorry Mark, I misunderstood what you were saying. The code I have for yealink_notify_xml.lua is given below. I don't remember writing it, but that doesn't mean I didn't! The file on my dev box is dated Sep 11 2020. --add the build_yealink_xml_body function function...

I completely agree with both of you. It is very easy to exceed your UDP packet size (MTU) these days. Using compact headers and reducing the number of codecs offered can help with this. Even using shorter domain names can be a help especially for large BLF NOTIFY messages. We have had...

The SIP protocol, is built on UDP for good reason. TCP is recommended as an alternative transport when certain UDP limitations are encountered. UDP has less overhead than TCP, because it is connectionless (fire and forget). TCP set up involves a three way handshake that all takes time to set...

Just something that I think we wrote to help someone out, no big deal. Happy New Year!

Andrew, there are many ways a transfer can be initiated and processed. Most of my customers use Yealink phones and they use the buttons on the phones to initiate the transfer. When the transfer button is used it causes the phone to send an in-dialog REFER message to initiate the transfer...

Early media with ring groups will always be problematic because codec negotiation is generally an end to end process, B2BUAs accepted. One A-leg cannot negotiate codecs with many potential B-legs. Almost everything is possible, it just requires research, and effort to implement. I believe...

No, it doesn't matter at all. I have used 15201, 15202... etc in the past, but you do need to make sure it doesn't conflict with the phones RTP port range. I meant to say that I have also come across odd NAT implementations before where two local IPs using the same port connecting to the same...

The configuration setting you are interested in is the sip.listen_port. Many Yealink phones have this under Settings->SIP rather than on a per account basis but I do believe that setting it at the account level works. The line(s) in the provision template looks like this: {if...