[OpenSIPS-Users] YNT: Re: OpenSIPS Load Balancer and OpenIMS integration

Tue Jun 3 08:03:45 CEST 2014

Hi all,

I have solved  403 not registered problem by changing P_is registered and P_assert_identity function in registration.c file of openims pcscf code .  There is cscf_get_ue_via function . It is is necessary to replace it with cscf_get_last_via.

Thanks for your support
Kaan

Samsung Mobile tarafından gönderildi

<div>-------- Orjinal mesaj --------</div><div>Kimden: ag at ag-projects.com </div><div>Tarih:30 05 2014  01:11  (GMT+02:00) </div><div>Alıcı: Kaan Dandin <kaandandin at yahoo.com> </div><div>Cc: OpenSIPS users mailling list <users at lists.opensips.org> </div><div>Konu: Re: [OpenSIPS-Users] OpenSIPS Load Balancer and OpenIMS integration </div><div>
</div>Your questions make no sense, this is nobody is answering them.

Adrian

On 29 May 2014, at 17:20, Kaan Dandin <kaandandin at yahoo.com> wrote:

Hi Bogdan,

Previously, I have asked some questions to you about OpenSIPS and OpenIMS integration.

My last situation is as following. I have shared it also with OpenIMS workgroup.
Could you please help me about this problem?

BR,
Kaan

Kime: openimscore-users at lists.berlios.de

Hi all,

I am building a test environment using OpenSIPS and OpenIMS.

As first step, I have successfuly installed OpenIMS and able to make registrations and start calls from Monster client.

As second step, I am  puttting OpenSIPS as load balancer between the IMS client and OpenIMS P-CSCF’s  .

I have installed OpenSIPS and “OpenSIPS Control Panel” successfully.

I have inserted the configuration to dispatcher module  from OpenSIPS Control Panel .

I can successfuly register to OpenIMS through OpenSIPS dispatcher module.

But when I try to make a call with Invite message after registration through OpenSIPS,
I get “403 Forbidden Not registered” error.

I have found a  thread in OpenIMS mailing group with a similar problem .
Could you please help me if there are any solution addressed for this issue until now.

http://lists.berlios.de/pipermail/openimscore-cscf/2010-January/001972.html

Error message coming from P-CSCF is following although the user is already successfully registered.

No.     Time        Source                Destination           Protocol Info
    415 220.825115  192.168.2.1           192.168.2.141         SIP      Status: 403 Forbidden - Not Registered! You must register first with a S-CSCF

Frame 415 (735 bytes on wire, 735 bytes captured)
Ethernet II, Src: Vmware_27:3f:bb (00:0c:29:27:3f:bb), Dst: Vmware_22:e0:4c (00:0c:29:22:e0:4c)
    Destination: Vmware_22:e0:4c (00:0c:29:22:e0:4c)
        Address: Vmware_22:e0:4c (00:0c:29:22:e0:4c)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
    Source: Vmware_27:3f:bb (00:0c:29:27:3f:bb)
        Address: Vmware_27:3f:bb (00:0c:29:27:3f:bb)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
    Type: IP (0x0800)
Internet Protocol, Src: 192.168.2.1 (192.168.2.1), Dst: 192.168.2.141 (192.168.2.141)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00)
    Total Length: 721
    Identification: 0x0000 (0)
    Flags: 0x04 (Don't Fragment)
    Fragment offset: 0
    Time to live: 64
    Protocol: UDP (0x11)
    Header checksum: 0xb22d [correct]
    Source: 192.168.2.1 (192.168.2.1)
    Destination: 192.168.2.141 (192.168.2.141)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Source port: sip (5060)
    Destination port: sip (5060)
    Length: 701
    Checksum: 0x3853 [correct]
Session Initiation Protocol
    Status-Line: SIP/2.0 403 Forbidden - Not Registered! You must register first with a S-CSCF
        Status-Code: 403
        [Resent Packet: False]
    Message Header
        Call-ID: a6f55ffd6540b7c6f70d03d6eb1ceb5f at 192.168.2.10
        CSeq: 182 INVITE
        From: <sip:alice at open-ims.test>;tag=1219
            SIP from address: sip:alice at open-ims.test
            SIP tag: 1219
        To: <sip:bob at open-ims.test>;tag=9ad9f37f74332c1e2a4045522a5bab87.f34e
            SIP to address: sip:bob at open-ims.test
            SIP tag: 9ad9f37f74332c1e2a4045522a5bab87.f34e
        Via: SIP/2.0/UDP 192.168.2.141:5060;branch=z9hG4bKe935.85ea0cd2.0;rport=5060
        Via: SIP/2.0/UDP 192.168.2.10:5062;branch=z9hG4bK1240af306e6063ca2275658fb7f8b4f9
        Server: Sip EXpress router (2.1.0-dev1 OpenIMSCore (i386/linux))
        Content-Length: 0
        Warning: 392 192.168.2.1:5060 "Noisy feedback tells:  pid=12954 req_src_ip=192.168.2.141 req_src_port=5060 in_uri=sip:bob at open-ims.test out_uri=sip:bob at open-ims.test via_cnt==2"

Previous thread is following:
[OpenIMSCore-CSCF] !P_is_registered()

"Martínez García, Rebeca"     remartinez at indra.es 
Tue Jan 19 13:54:05 CET 2010
Previous message: [OpenIMSCore-CSCF] !P_is_registered()
Next message: [OpenIMSCore-CSCF] p-cscf crash on: FIFO open for read failed > Too	many open files
Messages sorted by:               [ date ] [ thread ] [ subject ] [ author ]
Hello Franz,

I was not aware of these initiatives and, as I have been following TISPAN recommendations all the time, I took a look at TS 182 025. 
Nevertheless, we are not trying to implement a NGCN but to only develop a CNG. I will explain myself:

We had OpenIMSCore installed in 4 servers perfectly running and clients were able to register and call each other without problems 
(we had it configured for clients to send the REGISTER message directly to the P-CSCF).

The next step in our testbed was to create a group of private clients behind a gateway (CNG) which connected to OpenIMSCore. So the scenario 
is public clients (one machine at the moment) connect directly to P-CSCF and private clients do it via the CNG.

The development of the CNG has been fine until we tried to make work "CNG SIP Proxy/B2BUA" function (TS 183 003), which permits 
internal calls. The most simple configuration is to make it work as a Proxy, which implies that when seeing a REGISTER
message it saves locally their location and forwards the message to the P-CSCF (the rest of messages are forwarded in a transparent fashion).

But the problem is not in the register process, because private clients register without problems... the problem is when calling 
a public client. SER receives an INVITE and it forwards directly the message to the P-CSCF but it puts its Via.

Then the "cscf_get_ue_via" function inside the "P_is_registered()" one selects the first via (the one introduced by SER):
{
02197     struct via_body *vb=0;
02198         
02199     if (msg->first_line.type==SIP_REQUEST) vb = cscf_get_first_via(msg,0);
02200     else vb = cscf_get_last_via(msg);
02201     
02202     if (!vb) return 0;
02203     
02204     if (vb->port == 0) vb->port=5060;
02205     return vb;  
02206 }

and the P-CSCF rejects the INVITE because the "user is not registered".

Why does the Proxy-CSCF selects the first Via if it is a SIP REQUEST? (Just asking)

Thanks in advance,
Rebeca Martinez

BR,
Kaan

,

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140603/30728da7/attachment-0001.htm>