[SR-Users] smsops module - status report?

2020-08-13 Thread Pafel
Hello,
I am trying to generate sms status report using smsops module but without
success. I couldn't find any example on the net. Can somebody help me?

According to https://en.wikipedia.org/wiki/GSM_03.40 TP-MTI (tpdu(type) in
kamailio) should be "1 0" for status report. Delivery is "0 0" and submit
"0 1". According to the provided examples in smsops module:
tpdu(type) = 4 is delivery
tpdu(type) = 1 is submit
So what's the number for status? I could't find the mapping in the code.
Only this:
// Types of the PDU-Message
typedef enum _pdu_message_type {
DELIVER = 0x00,
SUBMIT = 0x01,
COMMAND = 0x02,
ANY = 0x03,
} pdu_message_type_t;

So any hint or example is appreciated.

Thanks,
Pavel Siderov
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] IMS RX AAR issues

2020-02-06 Thread Pafel
msg_apply_changes();
just before Rx_AAR did the job.

Now I can get the rewritten by rtpengine SDP media ip and port. Also the
Rx_AAR command/function is getting the correct values for ip and port.

Regards,
Pavel Siderov

На вт, 4.02.2020 г. в 12:39 Pafel  написа:

> Hello,
>
> I am using kamailio 5.3 + rtpengine module + sipwise rtpengine in a IMS
> test environment. I have and issue with ims_qos module and Rx AAR command.
>
> PCSCF is configured with
> #!define WITH_RX
>
>
> ##!define WITH_RX_REG
> #!define WITH_RX_CALL
>
> I have 2 test phones connected. Both of them use ipv6.
> PCSCF has ipv4 and ipv6 address.
> All other nodes - SCSCF, ICSCF use ipv4.
>
> Simple scenario UE1 calls UE2. UE2 is replying with 183 session progress
> and then RX AAR is sent by PCSCF to PCRF/PGW. The problem is that AVPs
> Media-Sub-Component Flow-Description include ipv4 address of the proxy and
> ipv6 address of the UE.
>
> Example:
> permit out 17 from 192.168.1.1 34998 to fd18::1:2dca:3303:1286:257d 50010
> permit in 17 from fd18::1:2dca:3303:1286:257d 50010 to 192.168.1.1 34998
>
> But this is not acceptable for the PGW (different ip versions).
> The SDP between UE and PCSCF is rewritten by rtpengine/sipwise. Looking at
> the ims_qos module I found that the address of the proxy is taken from the
> session original request SDP media ip/port. Having in mind that
> rtpengine/sipwise proxy is rewritting it is there any way I can set the
> correct ipv6 address and port of the proxy?
>
> I've tried to get the rewritten media address from SDP (in logs) but
> without success:
> if(sdp_get_line_startswith("$avp(cline)", "c=")) {
> xlog("L_INFO", "SDP media ip: $(avp(cline){s.select,2, })\n");
> }
> if(sdp_get_line_startswith("$avp(mline)", "m=")) {
>
>
> xlog("L_INFO", "SDP media port: $(avp(mline){s.select,1, })\n");
> }
> I am always getting the ipv4 media address and port of the proxy.
>
> Any idea how I can set and use the rewritten by the rtpengine/sipwise
> media ip and proxy for the RX AAR?
>
> Thanks in advance,
> Pavel Siderov
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] IMS RX AAR issues

2020-02-04 Thread Pafel
Hello,

I am using kamailio 5.3 + rtpengine module + sipwise rtpengine in a IMS
test environment. I have and issue with ims_qos module and Rx AAR command.

PCSCF is configured with
#!define WITH_RX


##!define WITH_RX_REG
#!define WITH_RX_CALL

I have 2 test phones connected. Both of them use ipv6.
PCSCF has ipv4 and ipv6 address.
All other nodes - SCSCF, ICSCF use ipv4.

Simple scenario UE1 calls UE2. UE2 is replying with 183 session progress
and then RX AAR is sent by PCSCF to PCRF/PGW. The problem is that AVPs
Media-Sub-Component Flow-Description include ipv4 address of the proxy and
ipv6 address of the UE.

Example:
permit out 17 from 192.168.1.1 34998 to fd18::1:2dca:3303:1286:257d 50010
permit in 17 from fd18::1:2dca:3303:1286:257d 50010 to 192.168.1.1 34998

But this is not acceptable for the PGW (different ip versions).
The SDP between UE and PCSCF is rewritten by rtpengine/sipwise. Looking at
the ims_qos module I found that the address of the proxy is taken from the
session original request SDP media ip/port. Having in mind that
rtpengine/sipwise proxy is rewritting it is there any way I can set the
correct ipv6 address and port of the proxy?

I've tried to get the rewritten media address from SDP (in logs) but
without success:
if(sdp_get_line_startswith("$avp(cline)", "c=")) {
xlog("L_INFO", "SDP media ip: $(avp(cline){s.select,2, })\n");
}
if(sdp_get_line_startswith("$avp(mline)", "m=")) {


xlog("L_INFO", "SDP media port: $(avp(mline){s.select,1, })\n");
}
I am always getting the ipv4 media address and port of the proxy.

Any idea how I can set and use the rewritten by the rtpengine/sipwise media
ip and proxy for the RX AAR?

Thanks in advance,
Pavel Siderov
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] rtpengine relay ip and port in avp

2020-01-31 Thread Pafel
Thanks for the info Yuri!

I tried several scenarios but without success. My sip proxy has ipv4
and ipv6 address. The other nodes use ipv4. When there is a request
for a ipv6 UAC/customer comming to the proxy the rtpengine/sipwise is
rewriting the sdp with the correct ipv6 address of the proxy. So I am
trying to get the ipv6 address of the proxy from the sdp (which is
always the same ipv6 address) and the port (which is always
different).

I've enabled

modparam("rtpengine", "write_sdp_pv", "$avp(sdp)")

And I have in request section:

rtpengine_manage($avp(rtpproxy_offer_flags));
set_body("$avp(sdp)", "application/sdp");
xlog("L_INFO", "Request SDP $avp(sdp))\n");

And the problem is that I am always getting the ipv4 address and port but
not the rewritten by the proxy ipv6 address and port.

Any idea?

Regards,
Pavel
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine relay ip and port in avp

2020-01-23 Thread Pafel
My bad, I am using rtpengine module but not rtpproxy.

Regards,
Pavel

На ср, 22.01.2020 г. в 18:41 Pafel  написа:

> Hello,
> I am using kamailio 5.3, rtproxy module and sipwise rtpengine. Is there
> any way I can get the rewritten / relay address and port by the
> rtpproxy/rtpengine. In avp or some other variable?
> Regards,
> Pavel Siderov
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] rtpengine relay ip and port in avp

2020-01-22 Thread Pafel
Hello,
I am using kamailio 5.3, rtproxy module and sipwise rtpengine. Is there any
way I can get the rewritten / relay address and port by the
rtpproxy/rtpengine. In avp or some other variable?
Regards,
Pavel Siderov
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] cdp avps issues in kamailio 5.2

2019-03-13 Thread Pafel
Hmm, strange. I've updated from 5.2.1 to 5.2.2 and now I got
host-ip-address in capabilities exchange request. After several tests I've
stopped pcscf and again host-ip-address is not present in request to hss.
Then again I've started pcscf and host-ip-address was present. During the
tests with 5.2.1 pcscf was started.. but host-ip-address wasn't available
in capabilities exchange. Anyway, now everything is ok. Thank you very much
for your help.

Regards,
Pavel Siderov

На ср, 13.03.2019 г. в 13:50 ч. Mojtaba  написа:

> The sound is strange, Actually the host-IP-Addres should not be missed in
> new version because it is mandatory option,
> I guess it would be nice to check it with latest version again.
> With Regards. Mojtaba
>
> On Wed, Mar 13, 2019 at 2:07 PM Pavel S  wrote:
>
>> Hello Mojtava,
>>
>> > Did you use FHOSS or IMS_DIAMETER_SERVER module?
>> No, I am using our own hss server.
>>
>> >Anyway what mandatory parameters do you mean exactly?
>> According to RFC6733 section 5.3.1 - 
>> https://tools.ietf.org/html/rfc6733#section-5.3.1
>>
>>The Capabilities-Exchange-Request (CER), indicated by the Command
>>Code set to 257 and the Command Flags' 'R' bit set, is sent to
>>exchange local capabilities.  Upon detection of a transport failure,
>>this message MUST NOT be sent to an alternate peer.
>>
>>When Diameter is run over SCTP [RFC4960] or DTLS/SCTP [RFC6083],
>>which allow for connections to span multiple interfaces and multiple
>>IP addresses, the Capabilities-Exchange-Request message MUST contain
>>one Host-IP-Address AVP for each potential IP address that MAY be
>>locally used when transmitting Diameter messages.
>>
>>   Message Format
>>
>>   ::= < Diameter Header: 257, REQ >
>>{ Origin-Host }
>>{ Origin-Realm }
>> 1* { Host-IP-Address }
>>{ Vendor-Id }
>>{ Product-Name }
>>[ Origin-State-Id ]
>>  * [ Supported-Vendor-Id ]
>>  * [ Auth-Application-Id ]
>>  * [ Inband-Security-Id ]
>>  * [ Acct-Application-Id ]
>>  * [ Vendor-Specific-Application-Id ]
>>[ Firmware-Revision ]
>>  * [ AVP ]
>>
>> Kamailio 5.1 with loaded cdp, cdr_avp, ims_icsf modules and default 
>> configuration described here 
>> https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/icscf 
>> sends Host-IP-Address but Kamailio 5.2 with the same configuration doesn't.
>>
>> Any idea how to fix it?
>>
>> Regards,
>>
>> Pavel Siderov
>>
>>
>> >Hello,
>> >The CER/CEA messages are used just for connections between two peers
>> >diameter interface. Did you use FHOSS or IMS_DIAMETER_SERVER module? In
>> >both cases, you should not have any issue. Anyway what mandatory parameters
>> >do you mean exactly?
>> >WIth Best Regards. Mojtava
>> ><https://www.kamailio.org/docs/modules/5.1.x/modules/ims_diameter_server.html>
>>
>> >On Tue, Mar 12, 2019 at 8:17 PM Pafel > ><https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote:
>> >
>> >>* Hello,
>> *>>>>* I am testing ims setup with kamailio 5.2 using the default 
>> configuration
>> *>>* provided here:
>> *>>* https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/ 
>> <https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/> .
>> *>>* Тhere is an issue I am facing with cdp avp in request sent to hss. There
>> *>>* are some missing mandatory parameters in capabilities exchange request 
>> like
>> *>*> 257 host-ip-address for example. Any idea how to add it via icscf.xml or
>> *>*> kamailio.cfg ? The same parameter is passed to hss with kamailio 5.1 
>> using
>> *>*> default ims configuration. I read cdp and cdp_avp documentation but
>> *>*> couldn't understand if it is possible to add it.
>> *>>>>* Regards,
>> *>>* Pavel Siderov
>> *>>* ___
>> *>>* Kamailio (SER) - Users Mailing List
>> *>>* sr-users at lists.kamailio.org 
>> <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>> *>*> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users 
>> <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>> *>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
> --
> --Mojtaba Esfandiari.S
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] cdp avps issues in kamailio 5.2

2019-03-12 Thread Pafel
Hello,

I am testing ims setup with kamailio 5.2 using the default configuration
provided here:
https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/ . Тhere
is an issue I am facing with cdp avp in request sent to hss. There are some
missing mandatory parameters in capabilities exchange request like 257
host-ip-address for example. Any idea how to add it via icscf.xml or
kamailio.cfg ? The same parameter is passed to hss with kamailio 5.1 using
default ims configuration. I read cdp and cdp_avp documentation but
couldn't understand if it is possible to add it.

Regards,
Pavel Siderov
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users