Search results

I just like OpenSIPs and use it with a company I consult for. Also, it has the built in cgrates and freeswitch modules. I'll take a look at the antifraud module, I wasn't aware of it or what it does. I do my own anti fraud using lookups basically on max connection fee and max cost per minute...

@Adrian Fretwell I think its going to be just a case of manually going through the script. I've actually gone the other way ie from Kamailio to Opensips. Why are you going to Kamailio by the way?

Get an sngrep of the internal call so you can see exactly what the phone is sending.

What OS are you using, I have installed without any problems like this a couple of times in the last couple of days.

You won't be able to use the packages on aws I wouldn't think as it is arm64 and the Pi packages are 32 bit. There's a good chance you will need to mod the installer script. No reason overall though why it shouldn't run on there.

Why do I need to create an account to see the pricing?

That would be transparent to the app, you would just configure a gateway as normal and the OS would choose to route using that nic based on your network configuration.

For a dedicated callcenter environment I wouldn't use FusionPBX. Use something like ViciDial instead.

That is the way it is designed, its is playing a continuous loop. Each person does not get the MOH from the beginning.

Yep, I may do too. I have always advocated that we should follow what the developer recommends.

I have questioned this myself more than once.

That's fine as long as you are aware. Its almost certain no changes are tested on Centos.

Just be aware this will likely put enormous stress upon your server.

The port setting for the external profile should be 5080 and 5060 for the internal.

I really would advise that you do not use Centos. You may be able to get it running on Centos but its certainly not the recommended OS. I see another post about Centos problems, do you really want to put a server into production on this kind of OS?

I have only just noticed your external profile is listening on port 5060, why is this?

I'll have to double check later but it was: failregex = \[WARNING\] sofia_reg.c:\d+ SIP auth failure \(REGISTER\) on sofia profile \'.*\' for \[.*\] from ip <HOST> I'm not sure whether it does a partial match, I didn't think it did.

The log entries should now look similar to: 2021-11-18 15:38:53.348548 98.93% [WARNING] sofia_reg.c:1861 SIP auth challenge That percentage before the [WARNING] is new.

You should have fs_cli open when you try it from the gui, then you should see, hopefully, what the error is.

I have a problem with Snoms occasionally. From one, lets call it a carrier, we receive a 180, freeswitch then sends this to the Snom endpoint as a 183. When the 200OK comes in, we get the real audio but there is a significant difference in the sequence number of the rtp packet. If we use...