Search results

Have you checked for sure that this is the format you are receiving the call in?

Also, I don't imagine it will take very long for them to realise they need to wait if they keep getting the wrong person.

I have just tried a new install on debian 11 and it appears to have installed without issue. I ran the install due to the comments in this thread in order to be able to report the problem to @markjcrane but I cannot replicate it. I'm using the standard net installer by the way...

Yep, I also spend mucho time with RFC3261. Additionally, a book I buy every realease of is https://www.amazon.co.uk/SIP-Understanding-Session-Initiation-Protocol-ebook/dp/B01BLTPMJ2 You can find PDFs etc floating around the net but I always have my hardback version floating around and within...

I think when I looked at it it was pretty basic, I'd personally probably favour the opensips bootcamp over that. You learn opensips but also learn about SIP at the same time. https://opensips.org/training/OpenSIPS_eBootcamp_2022/

Paste a siptrace of a call

Same here just a diaplan that adds a prefix on the outbound route.

Try making the call and using sngrep to get a log

A couple of years old but may help:

You have to be wary though unless you REALLY are confident and can debug because future fusionpbx develpment will not take this code into account and something could well break it.

I may be wrong but this feature was once in but caused other problems.

Not that this is a fix but remember too that we don't even need to use $1 for this, ie: action bridge sofia/gateway/skyetel.SE1/911 etc The destination is fixed so we can always put this In Europe 112 is an emergency number and in the UK it is 999 One of my carriers only accepts 999 so I...

Cool, I'm going to move this to tips and tricks

https://www.ietf.org/rfc/rfc3326.txt 3.1 Call Completed Elsewhere A proxy forks an INVITE request and one of the branches returns a 200 (OK). The forking proxy includes this status code in a Reason header field in the CANCEL request that it sends to the rest of the branches.

In a ring group, I'm almost certain, the cancel message is sent with a reason code, "call completed elsewhere", that should stop a missed call.

What endpoints are you using? Certainly, with ring groups, you should not be getting a missed call.

I don't think you can nest ring groups, ie ring group within ring group. I could be wrong though. Regardless, you do not need multiple just add the others to the same ring group but put a delay on.

Yes, though its not a very nice thing to do if you are not a member. Is open source though so nothing stopping you.

Bin the old pbx and take the plunge now, you are only delaying the inevitable anyway and you will get so much more functionality.

I have looked at this further, you have to allow the ip in the remote settings on the phone and the first time it will ask on the screen if it is OK to allow remote control but from then on, something like this works just fine: curl 'https://username:password@ipaddress/servlet?key=Reboot' -k...