It is very possible that your UDP packets are being fragmented because they are too big and that is why the calls are not working.
TCP will not suffer from this problem.
Using TCP for SIP is not a problem, all the media streams, eg audio/video still use UDP anyway.
What is your destination entry for this look like?
The answer would appear to be here:
a1a63f08-cb55-4a47-8a3e-3eaa43db4cbb 2023-09-14 03:43:30.980362 99.07% [ERR] switch_core_session.c:2760 Invalid Application
It looks like it is trying to call an invalid application.
So freeswitch is clearly listening there on UDP on the internal profile:
udp 0 0 172.26.9.223:5060
Are you saying the phones register OK with UDP?
On another note, why are you not using TCP anyway?
But if event guard is in play, they shouldn't be seen in the freeswitch cli.
Try restarting the event guard service, the iptables chains get created when the service starts.
Being a redis fan, because of its speed and the fact that it will be in memory, thats what I'd use.
Load the numbers into redis and then use a lua script in the dialplan to do the lookup.
My point is, if you just are trying to present a different caller id, you do not need multiple trunks if you are using a standard carrier.
I use one carrier with hundreds of caller IDs.
If you do really need a trunk per extension then just add a condition to the outbound route that matches the...
Have you set a specific caller ID in the outbound route? If not, this should just work.
Check the outgoing invite to the carrier with SNGREP to see if it is being sent to the cariier correctly and maybe the carrier is overriding it.
What is this order 195 you are referring to? Your 195 may not be the same as mine.
Everything that you can set in the webui should be available to set in provisioning, variables may need to be added to the template if they are not already there but it is doable. The gui helps with this.
For...
Hi,
Everything is probably working as expected. I'm not familiar with Grandstream but it looks like the phones are set to autoprovision at boot.
Ideally, you want the BLFs etc set in the device config so that the server provisions the buttons otherwise you will always face this situation when...