[SR-Users] Kamailio multidomain IMS

[Valentin Christoph via sr-users]

Dear IMS enthusiasts :-)

Has anyone experience with Kamailio IMS (CSCF) setups, where users with 
different domain names can be registered at one and the same S-CSCF?

Is this feasible at all?

I mean one IMS for users @ims1.example.com, @ims2.example.com, 
@ims3.example.com, in one and the same S-CSCF, I-CSCF, P-CSCF.

Thanks,
Christoph
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] $dlg_var() not implemented in ims_dialog module

[Valentin Christoph via sr-users]

Dear all,

I would probably need to store some dialog scoped information in an IMS 
environment, but the ims_dialog module does not implement the $dlg_var() pseudo 
variable.

Do you know other, maybe better, possibilities to store dialog scoped 
information in an IMS (CSCF) environment?

Thank,
Christoph
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Question for RFC junkies / kamailio modifying message bodies

[Valentin Christoph via sr-users]

Hi all,

it might be a minor issue, or it might not be an issue at all, but I stumbled 
over following statements in RFC 3261:

Chapter 16.6 Request Forwarding (of a proxy)


  1. Copy request



 The proxy starts with a copy of the received request.  The copy

 MUST initially contain all of the header fields from the

 received request.  Fields not detailed in the processing

 described below MUST NOT be removed.  The copy SHOULD maintain

 the ordering of the header fields as in the received request.

 The proxy MUST NOT reorder field values with a common field

 name (See Section 
7.3.1).  The proxy 
MUST NOT add to, modify,

 or remove the message body.



 An actual implementation need not perform a copy; the primary

 requirement is that the processing for each next hop begin with

 the same request.

Chapter 16.7 Response Processing (at a proxy)


  9.  Forward response



 After performing the processing described in steps "Aggregate

 Authorization Header Field Values" through "Record-Route", the

 proxy MAY perform any feature specific manipulations on the

 selected response.  The proxy MUST NOT add to, modify, or

 remove the message body.  Unless otherwise specified, the proxy

 MUST NOT remove any header field values other than the Via

 header field value discussed in Section 
16.7 Item 3.  In

 particular, the proxy MUST NOT remove any "received" parameter

On the other hand, everywhere in the Internet (starting with stackoverflow), 
you can read it is OK, if a SIP proxy modifies a body, and also kamailio allows 
it.

Might be a question for the coffee break.

All the best
Christoph
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Add XML to INVITE

[Valentin Christoph via sr-users]

Hi David,

I am always very cautious when using msg_apply_changes() – e.g. there are some 
implications with Record-Route, afaik

I do it this way:

set_body("--outer\r\nContent-Type:application/sdp\r\n\r\n$rb" +

"\r\n--outer\r\nContent-Type:application/vnd.3gpp.mcptt-info+xml\r\n\r\n" +
"\r\n" +


"\t\r\n" +

"\r\n--outer--\r\n",

"multipart/mixed;boundary=\"outer\"");

Hope this helps, and sorry for slow reaction. I am scanning the mailing list in 
rather low frequency.

Kr

From: David Villasmil via sr-users 
Sent: Tuesday, March 5, 2024 7:08 PM
To: Kamailio (SER) - Users Mailing List 
Cc: David Villasmil 
Subject: [SR-Users] Re: Add XML to INVITE

Hello guys,

Anyone on this?

Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337


On Sun, Mar 3, 2024 at 4:01 AM David Villasmil 
mailto:david.villasmil.w...@gmail.com>> wrote:
Hello guys,

I'm trying to add an xml with a boundary to an outgoing INVITE. But if i do:

set_body_multipart("$rb", "application/sdp", "delimiter");
msg_apply_changes();
append_body_part("$var(something)", "application/pidf+xml");
msg_apply_changes();

but kamailio adds the SDP, but NOT the second $var(something). If i switch them 
and add firs the var, and then the SDP. kamailio adds the contents of 
$var(something) but NOT the SDP point is it doesn't add the second append


Thanks!!!


Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: dispatcher - sip options per gw

[Valentin Christoph via sr-users]

And use the flag 8,  according

Optionally, these fields can be followed by:

flags - control the mode of using the destination address and sending 
keepalives. It is a bitwise value that can be built using the following flags:

1 (bit at index 0 - 1 <<0) - inactive destination

2 (bit at index 1 - 1 <<1) - temporary trying destination (in the way to become 
inactive if it does not reply to keepalives - there is a module parameter to 
set the threshold of failures)

4 (bit at index 2 - 1 <<2) - admin disabled destination

8 (bit at index 3 - 1 <<3) - probing destination (sending keep alives);

16 (bit at index 4 - 1 <<4) - skip DNS A/ resolve at startup, useful when 
the hostname of the destination address is a NAPTR or SRV record only. Such 
addresses cannot be matched anymore with ds_is_from_list(...).

-Original Message-
From: Valentin Christoph
Sent: Tuesday, March 5, 2024 7:04 PM
To: Kamailio (SER) - Users Mailing List 
Cc: marek 
Subject: RE: [SR-Users] dispatcher - sip options per gw

You must set the module parameter

## probing mode 3 is necessary, if you want to selectively disable OPTIONS 
#!define DS_PROBING_MODE 3

# Actively query the gateways:
modparam("dispatcher", "ds_probing_mode", DS_PROBING_MODE)

Kr,
Christoph
-Original Message-
From: marek via sr-users 
Sent: Tuesday, March 5, 2024 2:10 PM
To: Kamailio (SER) - Users Mailing List 
Cc: marek 
Subject: [SR-Users] dispatcher - sip options per gw

hi,

i have kamailio gw (5.6.x) for voxbone. dispatcher module

voxbone has separated inbound/outboud and prohibit sip options to "inbound" IP


#traffic from voxbone

20 sip:81.201.82.45:5060;transport=udp 1 0 duid=abc;socket=udp:x.x.x.x:5060

#traffic TO voxbone

30 sip:81.201.89.110:5060;transport=udp 0 0 duid=abc;socket=udp:x.x.x.x:5060


is it possible send sip options per GW with dispatcher module?

i tried flag "1 (bit at index 0 - 1 <<0) - inactive destination"

https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#idm1059


Marek

__
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send 
an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: dispatcher - sip options per gw

[Valentin Christoph via sr-users]

You must set the module parameter

## probing mode 3 is necessary, if you want to selectively disable OPTIONS
#!define DS_PROBING_MODE 3

# Actively query the gateways:
modparam("dispatcher", "ds_probing_mode", DS_PROBING_MODE)

Kr,
Christoph
-Original Message-
From: marek via sr-users 
Sent: Tuesday, March 5, 2024 2:10 PM
To: Kamailio (SER) - Users Mailing List 
Cc: marek 
Subject: [SR-Users] dispatcher - sip options per gw

hi,

i have kamailio gw (5.6.x) for voxbone. dispatcher module

voxbone has separated inbound/outboud and prohibit sip options to "inbound" IP


#traffic from voxbone

20 sip:81.201.82.45:5060;transport=udp 1 0 duid=abc;socket=udp:x.x.x.x:5060

#traffic TO voxbone

30 sip:81.201.89.110:5060;transport=udp 0 0 duid=abc;socket=udp:x.x.x.x:5060


is it possible send sip options per GW with dispatcher module?

i tried flag "1 (bit at index 0 - 1 <<0) - inactive destination"

https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#idm1059


Marek

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Question syntax check / plausi check kamailio.cfg

[Valentin Christoph via sr-users]

Dear all,

Is there any other possibility to (automatically) check the plausibility/syntax 
of an existing kamailio.cfg, besides

kamailio -c -f kamailio.cfg

?

Thanks,
Christoph
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe: