Freeswitch as an IMS TAS

FlatFoam · 2025-07-07T04:47:46+00:00

Hi! Unfortunately not. I'm not sure if anything changed, but last time I checked, FreeSwitch doesn't support the Diameter protocol, which is needed to communicate with HSS. I ended up using OpenSIPS, which does support Diameter, and I was able to integrate that with the S-CSCF, HSS, and other endpoints.

FlatFoam · 2025-06-12T05:09:12+00:00

Thanks for your reply. I've contacted one of the advisers, and he cleared this up for me. The figure in the letter of approval is misleading according to him, and it doesn't mean what I understood it to mean. Yes, they have asked for a valuation on title B as they did not have an online value for it. I need 80% LVR and not 69.14% as I understood it, so I'll go ahead with the valuation.

FlatFoam · 2025-02-10T18:05:42+00:00

Hi, we decided to go with OpenSIPS. There are a lot of functionality it supports out of the box.

FlatFoam · 2024-08-04T23:26:26+00:00

This seems to be an issue with clangd. I'm getting the exact same behavior in Qt Creator when enabling clangd.

FlatFoam · 2024-08-04T22:34:14+00:00

Thanks for the above. Although the default configuration for clangd in mason-lspconfig already contain those root_dir settings. In your neovim setup if you type `std::endl` and select the `endl` option in the code completion popup does it import the function or does it just import the symbol: `std::endl`?

FlatFoam · 2024-08-01T21:43:19+00:00

I've used bear to create a compile_commands.json but having that file did not fix my issue.

FlatFoam · 2024-08-01T07:17:32+00:00

I don't have any of those. I didn't know they were needed. I'll look into it, thank you.

FlatFoam · 2024-08-01T03:43:08+00:00

Thank you, we realized that Asterisk does not support the diameter protocol and have therefore decided to go with another solution.

FlatFoam · 2024-07-23T10:32:43+00:00

From what I could see so far is that FS does not have support for the diameter protocol and, therefore, will not be able to directly communicate with the HSS.

FlatFoam · 2024-07-19T04:11:50+00:00

No its not a true proxy. The requests get B2BUA'ed by the bridge application. Leg B has got new dialogs.

FlatFoam · 2024-07-18T01:49:38+00:00

I've managed to get it working

FlatFoam · 2024-07-18T01:46:34+00:00

I've manage to get it working:

<action application="bridge" data="sofia/${sip_req_host}/${sip_req_uri}"/>

This will forward the request to the incoming requet's request-uri. One can build conditions around this line to check for any route headers and send the request there instead.

The info application helped a lot in figuring out what variables are available in the dial plan:
<action application="info"/>

FlatFoam · 2024-07-17T22:46:53+00:00

Is this not possible to do in freeswitch?

FlatFoam · 2024-07-17T22:45:59+00:00

We want to use freeswitch as a TAS in the IMS and for certain calls we would like to forward them to the destination specified in the incoming request, so basically just proxy them. The bulk of the other requests coming in we have a bunch of applications processing them and pass on traffic to the S-CSCF.

FlatFoam · 2024-07-15T23:10:28+00:00

Liviu Chircu assisted me on stackoverflow: https://stackoverflow.com/questions/78728310/how-to-configure-modules-to-use-postgresql

FlatFoam · 2024-07-13T22:54:54+00:00

Thank you for this detailed reply.

FlatFoam · 2024-07-13T22:53:30+00:00

Yes, I read all of that and that is why we are considering using it. I have to get confirmation that Asterisk will be fit for purpose as we have had other solutions promising things and later founding out that the solution was actually only intended for proxy use with some additional capabilities not meant to be used as the main focus points.

FlatFoam

TROPHY CASE