[OpenSIPS-Users] Can anyone help me?!?

Mauro Davi' mauro.davi at acotel.com
Tue Feb 3 15:44:28 CET 2009


Hi All,
 
I setting Up an architecture with a SIP Proxy that using the dispatcher
module to
balance the incoming traffic on several SIP Servers.
 
 
            +----------+               +----------+
            |    UA1   |               |    UA2   |
            +----------+               +----------+
                ^ |                        ^ |
                | V                        | V
              +--------------------------------+
              |            SIP Proxy           |
              +--------------------------------+
                              ^ |
                              | V
                     +------------------+
                     | SIP Server (UAS) |
                     +------------------+
 
The SIP Proxy is an opensips server configured with the
opensipslbnew.cfg file attached.
The SIP Server is an opensips server configured with the
opensipsservernew.cfg file attached.
 
  UAC1 (.54)          Proxy (.73:4530)   UAS (.75:5060)          UAC2
(.71)
   |    INVITE          |                 |                       |
   |------------------->|                 |                       |
   |    100 Trying      |                 |                       |
   |<-------------------|     INVITE      |                       |
   |                    |---------------->|                       |
   |                    |   100 Trying    |                       |
   |                    |<----------------|                       |
   |                    |     INVITE      |                       |
   |                    |<----------------|                       |
   |                    |   100 Trying    |                       |
   |                    |---------------->|                       |
   |                    |                 |   INVITE              |
   |                    |---------------------------------------->|
   |                    |  180 RINGING    |                       |
   |                    |<----------------------------------------|
   |                    |  180 RINGING    |                       |
   |                    |---------------->|                       |
   |                    |  180 RINGING    |                       |
   |                    |<----------------|                       |
   |      180 RINGING   |                 |                       |
   |<-------------------------------------|                       |
   |                    |                 |  200 OK SDP           |
   |                    |<----------------------------------------|
   |                    |  200 OK SDP     |                       |
   |                    |---------------->|                       |
   |                    |  200 OK SDP     |                       |
   |                    |<----------------|                       |
   |      200 OK SDP    |                 |                       |
   |<-------------------------------------|                       |
   |                    |                 |                       |
   |       ACK (1)      |                 |                       |
   |------------------->|                 |                       |
   |                    |       ACK (2)   |                       |
   |                    |---------------->|                       |
   |                    |       ACK (3)   |                       |
   |                    |               +-|                       |
   |                    |               +>|                       |
   |                    |       ACK (4)   |                       |
   |                    |<----------------|                       |
   |                    |                 |                       |

 

During the setup phase (i.e. the INVITE message), the flow messages
seems to be correct, but when

The UAC1 send the following ACK message:

 

MESSAGE ACK (1)

 

Request-Line: ACK
sip:user1 at 192.168.193.75:5060;rinstance=79fc784dcae82199 SIP/2.0

Via: SIP/2.0/UDP
192.168.193.54:53166;branch=z9hG4bK-d8754z-3c65f53e8a006949-1---d8754z-;
rport

Max-Forwards: 70

Route: <sip:192.168.193.73:4530;lr;ftag=3129a447;nat=yes>

Route: <sip:192.168.193.75;lr=on;ftag=3129a447;nat=yes>

Route: <sip:192.168.193.73:4530;lr;ftag=3129a447;nat=yes>

Contact: <sip:user2 at 192.168.193.54:53166>

To: <sip:user1 at domain.com>;tag=1b6c6a0b

From: <sip:user2 at domain.com>;tag=3129a447

Call-ID: MjZhNjE4NGVmNTA0MTRmYjBkMjYxYmE4OWRmODVmYjM.

CSeq: 2 ACK

User-Agent: Bria release 2.4.3 stamp 50900

Content-Length: 0

 

The message is correctly routed by the Proxy to the UAS, that received
the below message:

 

MESSAGE ACK (2)

 

Request-Line: ACK
sip:user1 at 192.168.193.75:5060;rinstance=79fc784dcae82199 SIP/2.0

Method: ACK

Via: SIP/2.0/UDP 192.168.193.73:4530;branch=z9hG4bK3d0a.008192b2.2

Via: SIP/2.0/UDP
192.168.193.54:53166;received=192.168.193.54;branch=z9hG4bK-d8754z-3c65f
53e8a006949-1---d8754z-;rport=53166

Max-Forwards: 69

Route: <sip:192.168.193.75;lr=on;ftag=3129a447;nat=yes>

Route: <sip:192.168.193.73:4530;lr;ftag=3129a447;nat=yes>

Contact: <sip:user2 at 192.168.193.54:53166>

To: <sip:user1 at domain.com>;tag=1b6c6a0b

From: <sip:user2 at domain.com>;tag=3129a447

Call-ID: MjZhNjE4NGVmNTA0MTRmYjBkMjYxYmE4OWRmODVmYjM.

CSeq: 2 ACK

User-Agent: Bria release 2.4.3 stamp 50900

Content-Length: 0

 

 but this last network element resend the message to itself :-(....

 

Request leaving server,
D-URI='sip:192.168.193.75;lr=on;ftag=3129a447;nat=yes' - M=ACK
RURI=sip:192.168.193.73:4530; lr;ftag=c757db43;nat=yes
F=sip:user2 at domain.com T=sip:user1 at domain.com IP=192.168.193.73 ID=:
MjZhNjE4NGVmNTA0MTRmYjBkMjYxYmE4OWRmODVmYjM.

 

MESSAGE ACK (3)

 

ACK sip:192.168.193.73:4530;lr;ftag=c757db43;nat=yes SIP/2.0

Via: SIP/2.0/UDP 192.168.193.75;branch=z9hG4bK156e.fa185536.2

Via: SIP/2.0/UDP
192.168.193.73:4530;rport=4530;received=192.168.193.73;branch=z9hG4bK3d0
a.008192b2.2

Via: SIP/2.0/UDP
192.168.193.54:53166;received=192.168.193.54;branch=z9hG4bK-d8754z-3c65f
53e8a006949-1---d8754z-;rport=53166

Max-Forwards: 68

Route: <sip:192.168.193.75;lr=on;ftag=c757db43;nat=yes>

Contact: <sip:user2 at 192.168.193.73:4530>

To: <sip:user1 at domain.com>;tag=1b6c6a0b

From: <sip:user2 at domain.com>;tag=3129a447

Call-ID: MjZhNjE4NGVmNTA0MTRmYjBkMjYxYmE4OWRmODVmYjM.

CSeq: 2 ACK

User-Agent: Bria release 2.4.3 stamp 50900

Content-Length: 

 

The UAS don't delete the route field in the SIP message (.75), but
delete the Route field of the Proxy (.73). Add correctly the VIA field,
but route the message to itself.

Below there is the last message sent to the proxy, how you can see the
message pass throw the SIP server two times...

 

MESSAGE ACK(4)

 

Request-Line: ACK sip:192.168.193.73:4530;lr;ftag=3129a447;nat=yes
SIP/2.0

Method: ACK

Via: SIP/2.0/UDP 192.168.193.75;branch=z9hG4bK3d0a.b49415f4.2

Via: SIP/2.0/UDP
192.168.193.75;rport=5060;received=192.168.193.75;branch=
z9hG4bK156e.fa185536.2

Via: SIP/2.0/UDP
192.168.193.73:4530;rport=4530;received=192.168.193.73;branch=z9hG4bK3d0
a.008192b2.2

Via: SIP/2.0/UDP
192.168.193.54:53166;received=192.168.193.54;branch=z9hG4bK-d8754z-3c65f
53e8a006949-1---d8754z-;rport=53166

Max-Forwards: 67

Contact: <sip:user2 at 192.168.193.75:5060>

To: <sip:user1 at domain.com>;tag=1b6c6a0b

From: <sip:user2 at domain.com>;tag=3129a447

Call-ID: MjZhNjE4NGVmNTA0MTRmYjBkMjYxYmE4OWRmODVmYjM.

CSeq: 2 ACK

User-Agent: Bria release 2.4.3 stamp 50900

Content-Length: 0

 

I'm not a guru, I'm a principiant by I don't understand why the UAS has
this behaviour... The scripts (opensipsservernew.cfg) goes in the
loose_route() branch, that 

simply call a  t_route() function...

 

Could anyone help me please...

 

Thanks in Advance

    MD

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090203/d9bb929e/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opensipsservernew.cfg.tar.gz
Type: application/x-gzip
Size: 3771 bytes
Desc: opensipsservernew.cfg.tar.gz
Url : http://lists.opensips.org/pipermail/users/attachments/20090203/d9bb929e/attachment-0002.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opensipslbnew.cfg.tar.gz
Type: application/x-gzip
Size: 3847 bytes
Desc: opensipslbnew.cfg.tar.gz
Url : http://lists.opensips.org/pipermail/users/attachments/20090203/d9bb929e/attachment-0003.bin 


More information about the Users mailing list