Hi all,
im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers.
Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n
i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system.
currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with
originate sofia/gateway/kamailio/<number>@<outbound carrier IP>
to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable - no bandwith available". (maybe due to the internal ip-addresses within some of the headers?)
i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier.
i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow.
maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know.
TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers
any hint/help into the right direction is appreciated
Best Regards Christoph Russow
Hi all,
can no one help here? do you need more informations?
Best regards Christoph
Am 23.11.21 um 15:26 schrieb Christoph Russow:
Hi all,
im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers.
Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n
i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system.
currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with
originate sofia/gateway/kamailio/<number>@<outbound carrier IP>
to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable
- no bandwith available". (maybe due to the internal ip-addresses within
some of the headers?)
i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier.
i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow.
maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know.
TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers
any hint/help into the right direction is appreciated
Best Regards Christoph Russow
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Christoph,
so you have an trusted connection "SIPTRUNK" to kamailio (and then dispatcher to application/freeswitch B2BUA). I would create an now an vice-versa flow in your kamailio like this: FreeSWITCH (bridge/internal/kamailio-ip) to kamailio to SIPTRUNK.
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 09:01 Uhr schrieb Christoph Russow <russow@emtex.de
:
Hi all,
can no one help here? do you need more informations?
Best regards Christoph
Am 23.11.21 um 15:26 schrieb Christoph Russow:
Hi all,
im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers.
Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n
i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system.
currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with
originate sofia/gateway/kamailio/<number>@<outbound carrier IP>
to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable
- no bandwith available". (maybe due to the internal ip-addresses within
some of the headers?)
i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier.
i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow.
maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know.
TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers
any hint/help into the right direction is appreciated
Best Regards Christoph Russow
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
-- ________________________________________________________________
EMTEX GmbH Christoph Russow Software Engineer
Bischof-Otto-Weg 9 D-91086 Aurachtal Geschäftsführer: Markus Enzinger Tel. +49 9132 7490 0 Sitz der Gesellschaft: 91086 Aurachtal Fax. +49 9132 7490 900 Amtsgericht Fürth: HRB6804 ________________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
hi karsten,
yeah thats what i thought but i'm a bit without a clue here how to achieve this. any hints?
Best regards Christoph
Am 26.11.21 um 09:52 schrieb Karsten Horsmann:
Hi Christoph,
so you have an trusted connection "SIPTRUNK" to kamailio (and then dispatcher to application/freeswitch B2BUA). I would create an now an vice-versa flow in your kamailio like this: FreeSWITCH (bridge/internal/kamailio-ip) to kamailio to SIPTRUNK.
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 09:01 Uhr schrieb Christoph Russow <russow@emtex.de mailto:russow@emtex.de>:
Hi all, can no one help here? do you need more informations? Best regards Christoph Am 23.11.21 um 15:26 schrieb Christoph Russow: > Hi all, > > im currently trying to add a Outbound Proxying to our system which right > now does inbound loadbalancing for our application servers. > > Current: > Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n > > i now want to add the ability for our internal Application Servers to > terminate their outbound calls through the kamailio system. > > currently i've setup a gateway in the (freeswitch) application server > that has the kamailio system set as outbound-proxy. this leads to sip > calls started with > > originate sofia/gateway/kamailio/<number>@<outbound carrier IP> > > to be sent to the kamailio system which then forwards it to the given > carrier IP. Sadly our main carrier answers with "503 service unavailable > - no bandwith available". (maybe due to the internal ip-addresses within > some of the headers?) > > i've attached our current kamailio configuration and also a pcap of a > call i tried to start with our main carrier. > > i tried this way as it seemed to be the easiest way so our application > servers still can select the outbound carrier within their flow. > > maybe i'm on the wrong way here and need to solve this problem in a > completely different way i don't know. > > TLDR: sip proxying does not work as expected. need a way to achieve > outbound calls routed through kamailio from internal application servers > > any hint/help into the right direction is appreciated > > Best Regards > Christoph Russow > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > Important: keep the mailing list in the recipients, do not reply only to the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > -- ________________________________________________________________ EMTEX GmbH Christoph Russow Software Engineer Bischof-Otto-Weg 9 D-91086 Aurachtal Geschäftsführer: Markus Enzinger Tel. +49 9132 7490 0 Sitz der Gesellschaft: 91086 Aurachtal Fax. +49 9132 7490 900 Amtsgericht Fürth: HRB6804 ________________________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>-- Mit freundlichen Grüßen *Karsten Horsmann*
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Christoph,
its easier for the mailinglist members to help you, if they see that you tried something and show for example your config snippet where you have issues.
Right now its very hard to tell what to do.
So "i use configuration like in the shipped one with kamailio X.Y.Z and i didnt get the point how to identify my freeswitch as trusted for outbound and i used the default config https://github.com/kamailio/kamailio/blob/5.5.3/etc/kamailio.cfg#L566 and didnt get pstn route working."
As an example.
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 10:16 Uhr schrieb Christoph Russow <russow@emtex.de
:
hi karsten,
yeah thats what i thought but i'm a bit without a clue here how to achieve this. any hints?
Best regards Christoph
Hi Karsten,
i think the config i used is more or less the example config shipped with the current debian package besides adding the dispatcher module config and some special database lookup and selecting a special dispatcher group for "old" numbers stuff and removing registration and presence routing and nat(detection). i attached the complete config on my first email for reference.
the thing is kamailio routes calls to the selected carrier (freeswitch originates the call directly to the carriers ip and just uses kamailio as outbound_proxy the corresponding freeswitch config looks as follows for the gateway i use in the originate command: <include> <gateway name="kamailio"> <param name="proxy" value="192.168.10.180"/> <param name="outbound-proxy" value="192.168.10.180"/> <param name="register" value="false"/> <param name="caller-id-in-from" value="true"/> <param name="username" value="not-used"/> <param name="password" value="not-used"/> </gateway> </include> the originate command i use looks like: originate sofia/gateway/kamailio/<dstno>@<carrierip> ) but the carrier rejects it.
so my thought was that the carrier rejects it cause of the private IPaddresses within several headers (as seen in the pcap attached to my first mail as well) and i am now asking if somebody might have experienced the same and found a solution with my current setup or if im on the completely wrong track here and need to use something completely different that i don't know of right now.
what i want to achieve is that either our application servers them self select the target carrier based on the destination number the outbound call goes to and just use kamailio as proxy (which is what i tried and seemed to fail with the carrier) or that kamilio does that for me based on whatever rules with whatever module it needs and i originate the calls from the application servers to kamailio as the destination.
i just have no clue what would work best and how to solve my problem here and need a nudge in the right direction.
Hope that clears stuff up a bit. if something is still unclear please just ask.
Best regards Christoph
Am 26.11.21 um 10:31 schrieb Karsten Horsmann:
Hi Christoph,
its easier for the mailinglist members to help you, if they see that you tried something and show for example your config snippet where you have issues.
Right now its very hard to tell what to do.
So "i use configuration like in the shipped one with kamailio X.Y.Z and i didnt get the point how to identify my freeswitch as trusted for outbound and i used the default config https://github.com/kamailio/kamailio/blob/5.5.3/etc/kamailio.cfg#L566 https://github.com/kamailio/kamailio/blob/5.5.3/etc/kamailio.cfg#L566 and didnt get pstn route working."
As an example.
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 10:16 Uhr schrieb Christoph Russow <russow@emtex.de mailto:russow@emtex.de>:
hi karsten, yeah thats what i thought but i'm a bit without a clue here how to achieve this. any hints? Best regards Christoph
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
I solve this problem in Asterisk putting the outbound_proxy parameter in pjsip.conf.
outbound_proxy = sip:<kamailio_ip:5060>
On Tue, Nov 23, 2021, 11:32 AM Christoph Russow russow@emtex.de wrote:
Hi all,
im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers.
Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n
i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system.
currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with
originate sofia/gateway/kamailio/<number>@<outbound carrier IP>
to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable
- no bandwith available". (maybe due to the internal ip-addresses within
some of the headers?)
i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier.
i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow.
maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know.
TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers
any hint/help into the right direction is appreciated
Best Regards Christoph Russow
-- ________________________________________________________________
EMTEX GmbH Christoph Russow Software Engineer
Bischof-Otto-Weg 9 D-91086 Aurachtal Geschäftsführer: Markus Enzinger Tel. +49 9132 7490 0 Sitz der Gesellschaft: 91086 Aurachtal Fax. +49 9132 7490 900 Amtsgericht Fürth: HRB6804
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
hi,
thats what i did on our application servers (freeswitch gateway config). kamailio routes the calls as wanted but the carrier rejects it (see pcap file in first email).
best regards christoph
Am 26.11.21 um 10:56 schrieb Benedito Marques:
I solve this problem in Asterisk putting the outbound_proxy parameter in pjsip.conf.
outbound_proxy = sip:<kamailio_ip:5060>
On Tue, Nov 23, 2021, 11:32 AM Christoph Russow <russow@emtex.de mailto:russow@emtex.de> wrote:
Hi all, im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers. Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system. currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with originate sofia/gateway/kamailio/<number>@<outbound carrier IP> to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable - no bandwith available". (maybe due to the internal ip-addresses within some of the headers?) i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier. i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow. maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know. TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers any hint/help into the right direction is appreciated Best Regards Christoph Russow -- ________________________________________________________________ EMTEX GmbH Christoph Russow Software Engineer Bischof-Otto-Weg 9 D-91086 Aurachtal Geschäftsführer: Markus Enzinger Tel. +49 9132 7490 0 Sitz der Gesellschaft: 91086 Aurachtal Fax. +49 9132 7490 900 Amtsgericht Fürth: HRB6804 __________________________________________________________________________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Christoph,
sorry i overlooked that. Seems okay to me. So IMHO its "okay" in SIP.
Your Carrier didnt like it. First - i would try to ask the Carrier - The Error Message "503 Service Unavailable-No Bandwidth Available" seems to me like a blocking rule on the carrier side. Could be mixed +e164 (in To) vs e164 in From/PAI/whatever - the Contact-Header or something else.
The other way is to capture a working outbound call and then try to check what's different.
Best Karsten
Am Fr., 26. Nov. 2021 um 11:18 Uhr schrieb Christoph Russow <russow@emtex.de
:
hi,
thats what i did on our application servers (freeswitch gateway config). kamailio routes the calls as wanted but the carrier rejects it (see pcap file in first email).
yeah the only thing different are the private ips and the record-route headers.
the carrier needs a special request thats why the +e164 to and e164 everywhere else and the <prefix>e164 in invite header.
if i start the call directly from freeswitch to the carrier (without kamailio proxy) it works.
so i think maybe (as this is our main carrier) i need some other way to solve that.
Best regards Christoph
Am 26.11.21 um 12:56 schrieb Karsten Horsmann:
Hi Christoph,
sorry i overlooked that. Seems okay to me. So IMHO its "okay" in SIP.
Your Carrier didnt like it. First - i would try to ask the Carrier - The Error Message "503 Service Unavailable-No Bandwidth Available" seems to me like a blocking rule on the carrier side. Could be mixed +e164 (in To) vs e164 in From/PAI/whatever - the Contact-Header or something else.
The other way is to capture a working outbound call and then try to check what's different.
Best Karsten
Am Fr., 26. Nov. 2021 um 11:18 Uhr schrieb Christoph Russow <russow@emtex.de mailto:russow@emtex.de>:
hi, thats what i did on our application servers (freeswitch gateway config). kamailio routes the calls as wanted but the carrier rejects it (see pcap file in first email).
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Christoph,
you can also use the "topos" module to "hide" all the stuff:
https://kamailio.org/docs/modules/5.5.x/modules/topos.html
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 13:04 Uhr schrieb Christoph Russow <russow@emtex.de
:
yeah the only thing different are the private ips and the record-route headers.
the carrier needs a special request thats why the +e164 to and e164 everywhere else and the <prefix>e164 in invite header.
if i start the call directly from freeswitch to the carrier (without kamailio proxy) it works.
so i think maybe (as this is our main carrier) i need some other way to solve that.
Best regards Christoph
Hi all,
with help from Karsten (thanks again!) i figured out that this seems to be a problem with the carrier and not with my kamailio config as the carrier rejects all my calls from that newly authorized IP with the same error here.
I opened a ticket and hope that the problem will be solved this way.
Best regards Christoph Russow
Am 26.11.21 um 13:10 schrieb Karsten Horsmann:
Hi Christoph,
you can also use the "topos" module to "hide" all the stuff:
https://kamailio.org/docs/modules/5.5.x/modules/topos.html https://kamailio.org/docs/modules/5.5.x/modules/topos.html
Kind regards Karsten
Am Fr., 26. Nov. 2021 um 13:04 Uhr schrieb Christoph Russow <russow@emtex.de mailto:russow@emtex.de>:
yeah the only thing different are the private ips and the record-route headers. the carrier needs a special request thats why the +e164 to and e164 everywhere else and the <prefix>e164 in invite header. if i start the call directly from freeswitch to the carrier (without kamailio proxy) it works. so i think maybe (as this is our main carrier) i need some other way to solve that. Best regards Christoph
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Benedito Marques -
Christoph Russow -
Karsten Horsmann