date:20160205

Re: [SR-Users] Registration Failure - IMS

2016-02-05 Thread Franz Edler

Hello Cristina,

 

please add a tracefile of the registration generated with “tcpdump -i any -s 
3000 -w /var/tmp/trace.pcap”.

 

BR

Franz

 

From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of 
Cristina Caridi
Sent: Friday, February 5, 2016 9:26 AM
To: Jason Penton 
Cc: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Registration Failure - IMS

 

Hello, 

 

thank you for the responsive answer!

Ok, I will skip IP SEC mechanism for the moment :)

 

But I have another problem related to registration process. After REGISTER-401 
Unauthorized-REGISTER-200 OK, the IMS client sends the SUBSCRIBE message (for 
the "reg" event package subscription) to the S-CSCF, the latter replies with 
NOTIFY and the client correctly responds with 200 OK. In order to be notified 
on any change of registration state for the client, also the P-CSCF sends the 
SUBSCRIBE message to the S-CSCF, the S-CSCF sends a NOTIFY to the proxy but, 
instead of replying with 200 OK, the P-CSCF replies with 404-Not Here (like it 
doesn't recognize that the recipient of the NOTIFY in the Req-URI is the P-CSCF 
itself). 

 

Have you ever seen similar issue?

I've checked the S-CSCF database and it correctly contains the P-CSCF 
subscription. Can you suggest any workaround or I'm missing something?

 

Thank you for your support,

 

Cristina

 

 

 

2016-02-04 21:26 GMT+01:00 Jason Penton mailto:jason.pen...@smilecoms.com> >:

Hi Cristina,

Unfortunately IPSEC is not supported 100% on the P-CSCF at this time. There are 
pieces of code that exist for it but it is not something we focused on yet. 
Perhaps some of the other devs will get to it when they get the need or some 
spare time 

Cheers

Jason

 

On Thu, Feb 4, 2016 at 7:42 PM, Daniel-Constantin Mierla mailto:mico...@gmail.com> > wrote:

Hello,

maybe some other IMS guys are able to help more, but in general the 
authentication in handled in the configuration file of Kamailio by calling 
various auth functions. You have to spot where those are used and why is 
responding with 401. Eventually run it with debug=3 in kamailio.cfg to get more 
verbosity of what it is done in the code.

Also, it may help to check the emails from Franz Edler during January and 
February on this list, he provided configs and many details about building a 
prototype IMS platform. See next link and follow up discussion:

  - http://lists.sip-router.org/pipermail/sr-users/2016-January/091204.html

Cheers,
Daniel

On 03/02/16 11:58, Cristina Caridi wrote:

Hello,  

 

I'm a new starter of Kamailio (SER). I am using the version 4.4.0-dev6 in a 
Debian machine. 

I've configured all the IMS network elements, the FHoSS and also Boghe IMS/RCS 
client in a Windows machine. 

 

When an IMS user belonging to my network tries to register and IP SEC mechanism 
is enabled, the registration flow stops at 401 Unauthorized from S-CSCF -> 
I-CSCF -> P-CSCF -> client.

The problem is that the HSS in MAA message does not send the SIP-Auth-Data-item 
that should be cointain the Confidentiality Key and the Integrity Key; so the 
client is not able to challenge the S-CSCF sending another REGISTER message. 

 

Do you have any suggestions about this? When IP SEC is disabled (by managing 
client options), the registration works well.

Maybe is there any configuration at HSS level that i'm not considering?

 

Thank you in advance for your help, 

Cristina  

 

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org  
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users





-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org  
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




-- 



 


Jason Penton


Senior Manager: Applications and Services


Smile Communications Pty (Ltd)



Mobile:

+27 (0) 83 283 7000  


Skype:

jason.barry.penton


  jason.pen...@smilecoms.com


  www.smilecoms.com
   

 

 

This email is subject to the disclaimer of Smile Communications at 
http://www.smilecoms.com/home/email-disclaimer/

 

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio xmpp gateway configuration issue

2016-02-05 Thread Daniel-Constantin Mierla

Hello,

the error message tells that the module cannot connect to the xmpp
server. Is the xmpp server started and listening on the right port and
network interface?

Cheers,
Daniel


On 05/02/16 07:37, kevin hifx wrote:
> Dear friends,
>
> I am facing an issue, when trying to configure xmpp gateway between
> kamailio and ejabbred xmpp server.
>
> I have followed the steps mention in this web site:
> http://www.kamailio.org/docs/modules/4.1.x/modules/xmpp.html
>
> The kamailio service is running but in the log file it show that xmpp
> connection failed.
>
> "*Feb  5 11:32:33 sip-xmpp-server /usr/sbin/kamailio[646]: ERROR: xmpp
> [network.c:122]: net_connect(): connect() failed: Connection refused* "
>
> (Both kamailio and ejabbred installed on the same server in local
> network and have local DNS server)
>
> I have added following entries in the kamailio configuration file. I
> am only mentioning the xmpp section.
>
>
> "
> ### Global Parameters #
>
> alias=sip-xmpp.kevin.org 
>
> ### Modules Section 
> #!ifdef WITH_MYSQL
> loadmodule "db_mysql.so"
> #!endif
>
> loadmodule "mi_fifo.so"
> loadmodule "kex.so"
> loadmodule "corex.so"
> loadmodule "tm.so"
> loadmodule "tmx.so"
> loadmodule "sl.so"
> loadmodule "rr.so"
> loadmodule "pv.so"
> loadmodule "maxfwd.so"
> loadmodule "usrloc.so"
> loadmodule "registrar.so"
> loadmodule "textops.so"
> loadmodule "siputils.so"
> loadmodule "xlog.so"
> loadmodule "sanity.so"
> loadmodule "ctl.so"
> loadmodule "cfg_rpc.so"
> loadmodule "mi_rpc.so"
> loadmodule "acc.so"
>
> # XMPP
> loadmodule "xmpp.so"
>
> # - setting module-specific parameters ---
>
> modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo")
>
> modparam("rr", "enable_full_lr", 1)
>
> # XMPP
> modparam("xmpp", "domain_separator", "*")
> modparam("xmpp", "gateway_domain", "sip-xmpp.kevin.org
> ")
> modparam("xmpp", "xmpp_domain", "xmpp-sip.kevin.org
> ")
> modparam("xmpp", "xmpp_host", "xmpp.kevin.org ")
>
>
>
> ###XMPP
> # initial sanity checks -- messages with
> # max_forwards==0, or excessively long requests
> if (!mf_process_maxfwd_header("10")) {
> sl_send_reply("483","Too Many Hops");
> exit;
> };
>
> if (msg:len >=  2048 ) {
> sl_send_reply("513", "Message too big");
> exit;
> };
>
> ### absorb retransmissions ###
> if (!t_newtran()) {
> sl_reply_error();
> return;
> }
> if (method == "MESSAGE") {
> log("*** xmpp-handled MESSAGE message.\n");
> if (xmpp_send_message()) {
> t_reply("200", "Accepted");
> } else {
> t_reply("404", "Not found");
> }
> return;
> }
>
> log("*** xmpp: unhandled message type\n");
> t_reply("503", "Service unavailable");
> return;
> ###
>
> "
> could you please help me solve this issue.
>
>
>
> Thank you
> kevin
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Extending the default 1800 seconds of session expiration

2016-02-05 Thread Daniel-Constantin Mierla

Hello,

the server cannot increase it if the phone puts a value lower than you
want. You can send a response telling the client that the interval is
too short, specifying also the minimum value. I don't recall exactly the
header names right now, but should be easy to search in rfc3261.

Of course, if you just want to increase it in Kamailio side, that is
possible, but the phone might not expect it. You can change the Expires
header (or parameter for contact), then do msg_apply_changes() and then
handle the register/presence requests as usual.

Cheers,
Daniel

On 05/02/16 12:37, kssyrr wrote:
> Hello everyone,
>
> I am trying to extend the default 1800 seconds of session expiration
> (presence; kamctl ul show)... how do I do that?
>
> I Tried to change parameters in the dialog module + the stt module...
> no success.
> The session expiration time is still 1800 sec.
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] why msg_apply_changes() from REQUEST_ROUTE only

2016-02-05 Thread Daniel-Constantin Mierla

On 05/02/16 09:16, smititelu wrote:
> On 21.12.2015 10:48, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> in failure route the sip message is cloned in shared memory, with
>> many references to shared memory buffer, as well as shorter size
>> (just to fit the sip message) of the buffer storing the message (the
>> core used a private memory buffer to max capacity configured for
>> message size).
>
> I'm not sure where to I start working on this. Can you give some tips
> on the places/functions to look on and try to extend for failure routes?

First to look at is how the transaction structure is created -- see
t_newtran() as a starting point. Updating the content of the sip request
requires to do changes in the 'uas' structure of the transaction.

It may simplify by allocating more than the message buffer for the clone
in shared memory for transaction and then be sure that updated request
doesn't exceed the allocated buffer. Still, some other fields need to be
updated as well, as they point to the values inside the previous sip
message content.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found

2016-02-05 Thread Daniel-Constantin Mierla

Hello,

what is the version of kamailio you are using?

Can you show incoming INVITE and CANCEL as well as outgoing INVITE for
such call? You can replace IPs and other sensitive data with some other
values.

Do you get it for all CANCEL requests or only for some of them?

Cheers,
Daniel

On 05/02/16 15:50, Sid Mason wrote:
> Hi
>
> We are receiving error on CANCEL request from client that is supposed
> to be relayed to an Asterisk Server:
>
> [t_msgbuilder.c:490]: build_local_reparse(): ERROR:
> build_local_reparse: HDR_EOH_T was not found
>
> Any help on this is much appreciated.
>
>
> below is the log:
>
> Regards
> Sid
>
>  0(6351) DEBUG:  [parser/msg_parser.c:606]: parse_msg(): SIP
> Request:
>  0(6351) DEBUG:  [parser/msg_parser.c:608]: parse_msg():
>  method:  
>  0(6351) DEBUG:  [parser/msg_parser.c:610]: parse_msg():  uri:  
>>
>  0(6351) DEBUG:  [parser/msg_parser.c:612]: parse_msg():
>  version: 
>  0(6351) DEBUG:  [parser/parse_via.c:1254]: parse_via_param():
> Found param type 232,  =
> ; state=6
>  0(6351) DEBUG:  [parser/parse_via.c:1254]: parse_via_param():
> Found param type 235,  = ; state=17
>  0(6351) DEBUG:  [parser/parse_via.c:2642]: parse_via(): end of
> header reached, state=5
>  0(6351) DEBUG:  [parser/msg_parser.c:496]: parse_headers():
> parse_headers: Via found, flags=2
>  0(6351) DEBUG:  [parser/msg_parser.c:498]: parse_headers():
> parse_headers: this is the first via
>  0(6351) DEBUG:  [receive.c:134]: receive_msg(): After parse_msg...
>  0(6351) DEBUG:  [parser/parse_addr_spec.c:894]:
> parse_addr_spec(): end of header reached, state=10
>  0(6351) DEBUG:  [parser/msg_parser.c:173]: get_hdr_field():
> DEBUG: get_hdr_field:  [59];
> uri=[sip:0031xx...@voip03nl.voipsystem.com
> ]
>  0(6351) DEBUG:  [parser/msg_parser.c:175]: get_hdr_field():
> DEBUG: to body
> ["0031X" >
>  0(6351) DEBUG:  [parser/msg_parser.c:153]: get_hdr_field():
> get_hdr_field: cseq : <2> 
>  0(6351) DEBUG:  [parser/msg_parser.c:187]: get_hdr_field():
> DEBUG: get_hdr_body : content_length=0
>  0(6351) DEBUG:  [parser/msg_parser.c:89]: get_hdr_field():
> found end of header
> {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351)
> DEBUG:  [receive.c:177]: receive_msg(): preparing to run routing
> scripts...
> {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351)
> ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE]
> c=[/etc/kamailio/kamailio.cfg] l=614 a=5 n=route
> {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351)
> ERROR: *** cfgtrace:request_route=[REQINIT]
> c=[/etc/kamailio/kamailio.cfg] l=734 a=25 n=xlog
> {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351)
> ERROR:

Re: [SR-Users] Kamailio strange behaviour

2016-02-05 Thread Daniel-Constantin Mierla

You can always replace the real IP (and usernames/phone numbers) with
something else using a text editor, before posting to the mailing list.
If no details are given, it is hard to help.

Anyhow, in this case you provided some leads, respectively that you get
401 response. That could be because the password was wrong. You can run
kamailio with debug=3 and see what is printed when the phone fails to
register or use xlog() to print $rc after auth_check()..

Cheers,
Daniel

On 05/02/16 12:27, Gholamreza Sabery wrote:
> All of my clients are behind NAT! Unfortunately I can not put my
> captures here. The strange thing here for me is that:
> 1- Desktop can always REGISTER with all of my usernames.
> 2- My android phones can REGISTER with some usernames! For example if
> I have a 12 and a 17 username Android Linphone can REGISTER with 12
> but not with 17. Kamailio will always return a 401 error. This thing
> only happens on Android Linphone.
>
> I captured packets for both scenarios but nothing is strange about
> packets! How is this even possible?!!
>
> On Fri, Feb 5, 2016 at 1:25 PM, Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> received and rport are added when the client is behind NAT. Can
> you paste here the capture for the case that doesn't work? It will
> help us to see what is wrong there, and if not, could be that the
> mobile operator does some SIP ALG which breaks/blocks the sip, in
> this case you have to switch to tls.
>
> Cheers,
> Daniel
>
> On 05/02/16 07:35, Gholamreza Sabery wrote:
>> I am using Kamailio 4.1.x with NAT enabled. When I want to
>> REGISTER using my desktop client which is Linphone everything is
>> find with any username. But on Android some users can REGISTER
>> and someusers can not. I captured SIP packets and the only
>> difference between packets on Android devices and packets on
>> Desktop client is that on my desktop "received" and "rport" are
>> not added by Kamailio in response messages. Any idea on what is
>> happening here?
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org 
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> -- 
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda  - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> http://miconda.eu
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list
> sr-users@lists.sip-router.org 
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found

2016-02-05 Thread Sid Mason

 Hi

We are receiving error on CANCEL request from client that is supposed to be
relayed to an Asterisk Server:

[t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse:
HDR_EOH_T was not found

Any help on this is much appreciated.


below is the log:

Regards
Sid

 0(6351) DEBUG:  [parser/msg_parser.c:606]: parse_msg(): SIP Request:
 0(6351) DEBUG:  [parser/msg_parser.c:608]: parse_msg():  method:
 
 0(6351) DEBUG:  [parser/msg_parser.c:610]: parse_msg():  uri: <
sip:0031xx...@voip03nl.voipsystem.com>
 0(6351) DEBUG:  [parser/msg_parser.c:612]: parse_msg():  version:

 0(6351) DEBUG:  [parser/parse_via.c:1254]: parse_via_param(): Found
param type 232,  = ;
state=6
 0(6351) DEBUG:  [parser/parse_via.c:1254]: parse_via_param(): Found
param type 235,  = ; state=17
 0(6351) DEBUG:  [parser/parse_via.c:2642]: parse_via(): end of
header reached, state=5
 0(6351) DEBUG:  [parser/msg_parser.c:496]: parse_headers():
parse_headers: Via found, flags=2
 0(6351) DEBUG:  [parser/msg_parser.c:498]: parse_headers():
parse_headers: this is the first via
 0(6351) DEBUG:  [receive.c:134]: receive_msg(): After parse_msg...
 0(6351) DEBUG:  [parser/parse_addr_spec.c:894]: parse_addr_spec():
end of header reached, state=10
 0(6351) DEBUG:  [parser/msg_parser.c:173]: get_hdr_field(): DEBUG:
get_hdr_field:  [59]; uri=[sip:0031xx...@voip03nl.voipsystem.com]
 0(6351) DEBUG:  [parser/msg_parser.c:175]: get_hdr_field(): DEBUG:
to body ["0031X"
 0(6351) DEBUG:  [parser/msg_parser.c:153]: get_hdr_field():
get_hdr_field: cseq : <2> 
 0(6351) DEBUG:  [parser/msg_parser.c:187]: get_hdr_field(): DEBUG:
get_hdr_body : content_length=0
 0(6351) DEBUG:  [parser/msg_parser.c:89]: get_hdr_field(): found end
of header
{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351) DEBUG:
 [receive.c:177]: receive_msg(): preparing to run routing scripts...
{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351) ERROR:
*** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg]
l=614 a=5 n=route
{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351) ERROR:
*** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=734
a=25 n=xlog
{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.}  0(6351) ERROR:

[SR-Users] Extending the default 1800 seconds of session expiration

2016-02-05 Thread kssyrr


  
  
Hello everyone,

I am trying to extend the default 1800 seconds of session expiration
(presence; kamctl ul show)... how do I do that?

I Tried to change parameters in the dialog module + the stt
module... no success.
The session expiration time is still 1800 sec.
  


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio strange behaviour

2016-02-05 Thread Gholamreza Sabery

All of my clients are behind NAT! Unfortunately I can not put my captures
here. The strange thing here for me is that:
1- Desktop can always REGISTER with all of my usernames.
2- My android phones can REGISTER with some usernames! For example if I
have a 12 and a 17 username Android Linphone can REGISTER with 12 but not
with 17. Kamailio will always return a 401 error. This thing only happens
on Android Linphone.

I captured packets for both scenarios but nothing is strange about packets!
How is this even possible?!!

On Fri, Feb 5, 2016 at 1:25 PM, Daniel-Constantin Mierla 
wrote:

> Hello,
>
> received and rport are added when the client is behind NAT. Can you paste
> here the capture for the case that doesn't work? It will help us to see
> what is wrong there, and if not, could be that the mobile operator does
> some SIP ALG which breaks/blocks the sip, in this case you have to switch
> to tls.
>
> Cheers,
> Daniel
>
> On 05/02/16 07:35, Gholamreza Sabery wrote:
>
> I am using Kamailio 4.1.x with NAT enabled. When I want to REGISTER using
> my desktop client which is Linphone everything is find with any username.
> But on Android some users can REGISTER and someusers can not. I captured
> SIP packets and the only difference between packets on Android devices and
> packets on Desktop client is that on my desktop "received" and "rport" are
> not added by Kamailio in response messages. Any idea on what is happening
> here?
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing 
> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [SOLVED] Users in different domains and multiple domains

2016-02-05 Thread Barış Şekerciler

Thank you so much Daniel.
If I have a trouble I will type again :)

Regards.

> On 05 Feb 2016, at 11:47, Daniel-Constantin Mierla  wrote:
> 
> Hello,
> 
> yes, you can add multi-domain users by providing username@domain, like:
> 
> 
> kamctl add al...@wonderland.com  ...
> 
> Cheers,
> Daniel
> 
> On 05/02/16 09:18, Barış Şekerciler wrote:
>> Hi Daniel,
>> Thanks.
>> I'm wondering how can I add users to multi-domains with kamctl? Or is there 
>> anything which does the same job?
>> 
>> Regards. 
>> 
>> 
>> On 4 February 2016 at 19:45:54, Daniel-Constantin Mierla (mico...@gmail.com 
>> ) wrote:
>> 
>>> Hello,
>>> 
>>> look at the modules that you use and see if they have a parameter to enable 
>>> multi-domain support -- typically the use_domain module parameter needs to 
>>> be set to 1. If you look at the default kamailio.cfg for version 4.3.x, 
>>> there is a flag MULTIDOMAIN that you need to enable
>>> 
>>> Then you can use domain module to maintain the list of the local domain, or 
>>> if you have just few and not going to change, then you can use 'alias' 
>>> global parameter (it can be set many times with different domains).
>>> 
>>> Cheers,
>>> Daniel
>>> 
>>> On 04/02/16 14:45, Barış Şekerciler wrote:
 Hello everyone!
 I'm wondering something about Kamailio. Here is the idea:
 Such and example, I want to give base system which depends on Kamailio to 
 3 companies in 1 server.
 So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I have to 
 set a domain for each company, so total is I need 3 domains.
 
 For example a, b, c are users. But they should in the different domains 
 for know which is which. In a word, it should seems like this:
 
 a...@subdomain.domain.com 
 b...@subdomain.domain.com 
 c...@subdomain.domain.com 
 
 a...@subdomain2.domain.com 
 b...@subdomain2.domain.com 
 c...@subdomain2.domain.com 
 
 or
 
 a...@subdomain.domain2.com 
 b...@subdomain.domain2.com 
 c...@subdomain.domain2.com 
 
 etc...
 
 So where can I do this? Remember, Kamailio should in the 1 server and all 
 of domains and users should in this server (I will use Postgres)
 
 For more details, you can write.
 
 Thank you.
 Regards.
 
 
 ___
 SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
 sr-users@lists.sip-router.org 
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
 
>>> 
>>> --  
>>> Daniel-Constantin Mierla
>>> http://twitter.com/#!/miconda  - 
>>> http://www.linkedin.com/in/miconda 
>>> Book: SIP Routing With Kamailio - http://www.asipto.com 
>>> 
>>> http://miconda.eu 
>>> ___ 
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
>>> sr-users@lists.sip-router.org  
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
>>>  
> 
> -- 
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda  - 
> http://www.linkedin.com/in/miconda 
> Book: SIP Routing With Kamailio - http://www.asipto.com 
> 
> http://miconda.eu 
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio strange behaviour

2016-02-05 Thread Daniel-Constantin Mierla

Hello,

received and rport are added when the client is behind NAT. Can you
paste here the capture for the case that doesn't work? It will help us
to see what is wrong there, and if not, could be that the mobile
operator does some SIP ALG which breaks/blocks the sip, in this case you
have to switch to tls.

Cheers,
Daniel

On 05/02/16 07:35, Gholamreza Sabery wrote:
> I am using Kamailio 4.1.x with NAT enabled. When I want to REGISTER
> using my desktop client which is Linphone everything is find with any
> username. But on Android some users can REGISTER and someusers can
> not. I captured SIP packets and the only difference between packets on
> Android devices and packets on Desktop client is that on my desktop
> "received" and "rport" are not added by Kamailio in response messages.
> Any idea on what is happening here?
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Users in different domains and multiple domains

2016-02-05 Thread Daniel-Constantin Mierla

Hello,

yes, you can add multi-domain users by providing username@domain, like:


kamctl add al...@wonderland.com ...

Cheers,
Daniel

On 05/02/16 09:18, Barış Şekerciler wrote:
> Hi Daniel,
> Thanks.
> I'm wondering how can I add users to multi-domains with kamctl? Or is
> there anything which does the same job?
>
> Regards. 
>
>
> On 4 February 2016 at 19:45:54, Daniel-Constantin Mierla
> (mico...@gmail.com ) wrote:
>
>> Hello,
>>
>> look at the modules that you use and see if they have a parameter to
>> enable multi-domain support -- typically the use_domain module
>> parameter needs to be set to 1. If you look at the default
>> kamailio.cfg for version 4.3.x, there is a flag MULTIDOMAIN that you
>> need to enable
>>
>> Then you can use domain module to maintain the list of the local
>> domain, or if you have just few and not going to change, then you can
>> use 'alias' global parameter (it can be set many times with different
>> domains).
>>
>> Cheers,
>> Daniel
>>
>> On 04/02/16 14:45, Barış Şekerciler wrote:
>>> Hello everyone!
>>> I'm wondering something about Kamailio. Here is the idea:
>>> Such and example, I want to give base system which depends on
>>> Kamailio to 3 companies in 1 server.
>>> So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I
>>> have to set a domain for each company, so total is I need 3 domains.
>>>
>>> For example a, b, c are users. But they should in the different
>>> domains for know which is which. In a word, it should seems like this:
>>>
>>> a...@subdomain.domain.com
>>> b...@subdomain.domain.com
>>> c...@subdomain.domain.com
>>>
>>> a...@subdomain2.domain.com
>>> b...@subdomain2.domain.com
>>> c...@subdomain2.domain.com
>>>
>>> or
>>>
>>> a...@subdomain.domain2.com
>>> b...@subdomain.domain2.com
>>> c...@subdomain.domain2.com
>>>
>>> etc...
>>>
>>> So where can I do this? Remember, Kamailio should in the 1 server
>>> and all of domains and users should in this server (I will use Postgres)
>>>
>>> For more details, you can write.
>>>
>>> Thank you.
>>> Regards.
>>>
>>>
>>> ___
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --  
>> Daniel-Constantin Mierla
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Book: SIP Routing With Kamailio - http://www.asipto.com
>> http://miconda.eu
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Registration Failure - IMS

2016-02-05 Thread Cristina Caridi

Hello,

thank you for the responsive answer!
Ok, I will skip IP SEC mechanism for the moment :)

But I have another problem related to registration process. After
REGISTER-401 Unauthorized-REGISTER-200 OK, the IMS client sends the
SUBSCRIBE message (for the "reg" event package subscription) to the S-CSCF,
the latter replies with NOTIFY and the client correctly responds with 200
OK. In order to be notified on any change of registration state for the
client, also the P-CSCF sends the SUBSCRIBE message to the S-CSCF, the
S-CSCF sends a NOTIFY to the proxy but, instead of replying with 200 OK,
the P-CSCF replies with 404-Not Here (like it doesn't recognize that the
recipient of the NOTIFY in the Req-URI is the P-CSCF itself).

Have you ever seen similar issue?
I've checked the S-CSCF database and it correctly contains the P-CSCF
subscription. Can you suggest any workaround or I'm missing something?

Thank you for your support,

Cristina



2016-02-04 21:26 GMT+01:00 Jason Penton :

> Hi Cristina,
>
> Unfortunately IPSEC is not supported 100% on the P-CSCF at this time.
> There are pieces of code that exist for it but it is not something we
> focused on yet. Perhaps some of the other devs will get to it when they get
> the need or some spare time
>
> Cheers
> Jason
>
> On Thu, Feb 4, 2016 at 7:42 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> maybe some other IMS guys are able to help more, but in general the
>> authentication in handled in the configuration file of Kamailio by calling
>> various auth functions. You have to spot where those are used and why is
>> responding with 401. Eventually run it with debug=3 in kamailio.cfg to get
>> more verbosity of what it is done in the code.
>>
>> Also, it may help to check the emails from Franz Edler during January and
>> February on this list, he provided configs and many details about building
>> a prototype IMS platform. See next link and follow up discussion:
>>
>>   -
>> http://lists.sip-router.org/pipermail/sr-users/2016-January/091204.html
>>
>> Cheers,
>> Daniel
>>
>> On 03/02/16 11:58, Cristina Caridi wrote:
>>
>> Hello,
>>
>> I'm a new starter of Kamailio (SER). I am using the version 4.4.0-dev6 in
>> a Debian machine.
>> I've configured all the IMS network elements, the FHoSS and also Boghe
>> IMS/RCS client in a Windows machine.
>>
>> When an IMS user belonging to my network tries to register and IP SEC
>> mechanism is enabled, the registration flow stops at 401 Unauthorized from
>> S-CSCF -> I-CSCF -> P-CSCF -> client.
>> The problem is that the HSS in MAA message does not send the
>> SIP-Auth-Data-item that should be cointain the Confidentiality Key and the
>> Integrity Key; so the client is not able to challenge the S-CSCF sending
>> another REGISTER message.
>>
>> Do you have any suggestions about this? When IP SEC is disabled (by
>> managing client options), the registration works well.
>> Maybe is there any configuration at HSS level that i'm not considering?
>>
>> Thank you in advance for your help,
>> Cristina
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing 
>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
>> http://www.linkedin.com/in/miconda
>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
>
> --
>
> *Jason Penton*
> *Senior Manager: Applications and Services*
> *Smile Communications Pty (Ltd)*
> *Mobile:* +27 (0) 83 283 7000
> *Skype:* jason.barry.penton
> jason.pen...@smilecoms.com 
> www.smilecoms.com
>
>
>
> This email is subject to the disclaimer of Smile Communications at 
> http://www.smilecoms.com/home/email-disclaimer/ 
> 
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Users in different domains and multiple domains

2016-02-05 Thread Barış Şekerciler

Hi Daniel,
Thanks.
I'm wondering how can I add users to multi-domains with kamctl? Or is there 
anything which does the same job?

Regards. 


On 4 February 2016 at 19:45:54, Daniel-Constantin Mierla (mico...@gmail.com) 
wrote:

Hello,

look at the modules that you use and see if they have a parameter to enable 
multi-domain support -- typically the use_domain module parameter needs to be 
set to 1. If you look at the default kamailio.cfg for version 4.3.x, there is a 
flag MULTIDOMAIN that you need to enable

Then you can use domain module to maintain the list of the local domain, or if 
you have just few and not going to change, then you can use 'alias' global 
parameter (it can be set many times with different domains).

Cheers,
Daniel

On 04/02/16 14:45, Barış Şekerciler wrote:
Hello everyone!
I'm wondering something about Kamailio. Here is the idea:
Such and example, I want to give base system which depends on Kamailio to 3 
companies in 1 server.
So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I have to set a 
domain for each company, so total is I need 3 domains.

For example a, b, c are users. But they should in the different domains for 
know which is which. In a word, it should seems like this:

a...@subdomain.domain.com
b...@subdomain.domain.com
c...@subdomain.domain.com

a...@subdomain2.domain.com
b...@subdomain2.domain.com
c...@subdomain2.domain.com

or

a...@subdomain.domain2.com
b...@subdomain.domain2.com
c...@subdomain.domain2.com

etc...

So where can I do this? Remember, Kamailio should in the 1 server and all of 
domains and users should in this server (I will use Postgres)

For more details, you can write.

Thank you.
Regards.


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--  
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
___  
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list  
sr-users@lists.sip-router.org  
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users  
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] why msg_apply_changes() from REQUEST_ROUTE only

2016-02-05 Thread smititelu


On 21.12.2015 10:48, Daniel-Constantin Mierla wrote:

Hello,

in failure route the sip message is cloned in shared memory, with many 
references to shared memory buffer, as well as shorter size (just to 
fit the sip message) of the buffer storing the message (the core used 
a private memory buffer to max capacity configured for message size).


I'm not sure where to I start working on this. Can you give some tips on 
the places/functions to look on and try to extend for failure routes?


Regards,
Stefan
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Registration Failure - IMS

Re: [SR-Users] kamailio xmpp gateway configuration issue

Re: [SR-Users] Extending the default 1800 seconds of session expiration

Re: [SR-Users] why msg_apply_changes() from REQUEST_ROUTE only

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found

Re: [SR-Users] Kamailio strange behaviour

[SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found

[SR-Users] Extending the default 1800 seconds of session expiration

Re: [SR-Users] Kamailio strange behaviour

Re: [SR-Users] [SOLVED] Users in different domains and multiple domains

Re: [SR-Users] Kamailio strange behaviour

Re: [SR-Users] Users in different domains and multiple domains

Re: [SR-Users] Registration Failure - IMS

Re: [SR-Users] Users in different domains and multiple domains

Re: [SR-Users] why msg_apply_changes() from REQUEST_ROUTE only

15 matches

Site Navigation

Mail list logo

Footer information