Hi Bogdan, In attach there are the scripts files.
The load balancer route the INVITE request message to the sip server if it
received from an UAC otherwise it sent the request to the appropriate client
using a t_relay function.
All the subsequent message are routed in the loose_routed branch (also the ACK
request message).
below the 200 OK messagges sent by UAC2 to the proxy->server->proxy->UAC1.
UAC1 (.54) Proxy (.73:4530) UAS (.75:5060) UAC2(.71)
| | | 200 OK SDP (1) |
| |<----------------------------------------|
| | 200 OK SDP (2) | |
| |---------------->| |
| | 200 OK SDP (3) | |
| |<----------------| |
| 200 OK SDP (4) | | |
|<-------------------| | |
Message 200 OK from UAC2 -> Proxy (1)
2.0 200 OK
Via: SIP/2.0/UDP 192.168.193.73:4530;branch=z9hG4bKd8c4.6d562f91.0
Via: SIP/2.0/UDP
192.168.193.75;rport=5060;received=192.168.193.75;branch=z9hG4bKd8c4.a96eeb3.0
Via: SIP/2.0/UDP
192.168.193.73:4530;rport=4530;received=192.168.193.73;branch=z9hG4bKd8c4.5d562f91.0
Via: SIP/2.0/UDP
192.168.193.54:11780;received=192.168.193.54;branch=z9hG4bK-d8754z-843ba81c62397b3c-1---d8754z-;rport=11780
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.75;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Contact: <sip:[email protected]:28278;rinstance=92f44431ebda131f>
To: <sip:[email protected]>;tag=0f0b9372
From: <sip:[email protected]>;tag=a82ddc47
Call-ID: Y2Q3Njc0MjE0M2I2Mjk3NWQ0ZDNiNjI0YzAxMjgwNjI.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
Content-Type: application/sdp
User-Agent: Bria release 2.4.3 stamp 50900
Content-Length: 488
Message 200 OK from Proxy -> UAS (2)
[SDP payload]
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.193.75;rport=5060;received=192.168.193.75;branch=z9hG4bKd8c4.a96eeb3.0
Via: SIP/2.0/UDP
192.168.193.73:4530;rport=4530;received=192.168.193.73;branch=z9hG4bKd8c4.5d562f91.0
Via: SIP/2.0/UDP
192.168.193.54:11780;received=192.168.193.54;branch=z9hG4bK-d8754z-843ba81c62397b3c-1---d8754z-;rport=11780
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.75;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Contact: <sip:[email protected]:28278;rinstance=92f44431ebda131f>
To: <sip:[email protected]>;tag=0f0b9372
From: <sip:[email protected]>;tag=a82ddc47
Call-ID: Y2Q3Njc0MjE0M2I2Mjk3NWQ0ZDNiNjI0YzAxMjgwNjI.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
Content-Type: application/sdp
User-Agent: Bria release 2.4.3 stamp 50900
Content-Length: 488
[SDP payload]
Message 200 OK from UAS -> Proxy(3)
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.193.73:4530;rport=4530;received=192.168.193.73;branch=z9hG4bKd8c4.5d562f91.0
Via: SIP/2.0/UDP
192.168.193.54:11780;received=192.168.193.54;branch=z9hG4bK-d8754z-843ba81c62397b3c-1---d8754z-;rport=11780
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.75;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Contact: <sip:[email protected]:4530;rinstance=92f44431ebda131f>
To: <sip:[email protected]>;tag=0f0b9372
From: <sip:[email protected]>;tag=a82ddc47
Call-ID: Y2Q3Njc0MjE0M2I2Mjk3NWQ0ZDNiNjI0YzAxMjgwNjI.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
Content-Type: application/sdp
User-Agent: Bria release 2.4.3 stamp 50900
Content-Length: 488
[SDP payload]
Message 200 OK from Proxy -> UAC1(4)
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.193.54:11780;received=192.168.193.54;branch=z9hG4bK-d8754z-843ba81c62397b3c-1---d8754z-;rport=11780
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.75;lr;ftag=a82ddc47;nat=yes>
Record-Route: <sip:192.168.193.73:4530;lr;ftag=a82ddc47;nat=yes>
Contact: <sip:[email protected]:5060;rinstance=92f44431ebda131f>
To: <sip:[email protected]>;tag=0f0b9372
From: <sip:[email protected]>;tag=a82ddc47
Call-ID: Y2Q3Njc0MjE0M2I2Mjk3NWQ0ZDNiNjI0YzAxMjgwNjI.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
Content-Type: application/sdp
User-Agent: Bria release 2.4.3 stamp 50900
Content-Length: 488
[SDP payload]
The 200 OK message wad modified a first time by the server and a second time by
the proxy. I think that all the job are done by the TM module...
Best regards and Thanks so much.
MD
-----Messaggio originale-----
Da: Bogdan-Andrei Iancu [mailto:[email protected]]
Inviato: martedì 10 febbraio 2009 12:58
A: Mauro Davi'
Cc: [email protected]
Oggetto: Re: [OpenSIPS-Users] Can anyone help me?!?
Hello Mauro,
Please post the 200 OK received by the UA1 from the SIP proxy . This is
strange is that the ACK has in RURI the IP of the SIP Server (.75),
instead of the IP of the UA2.
A possibility is that the Contact from 200 OK (which will be used as
RURI for ACK) to be re-written by one of the parties....I suspect that
SIP proxy is doing that....try to follow the whole path of the 200 OK
from UA2 to UA1 and see where the contact is replaced.
Regards,
Bogdan
Mauro Davi' wrote:
> 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:[email protected]: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:[email protected]:53166>
>
> To: <sip:[email protected]>;tag=1b6c6a0b
>
> From: <sip:[email protected]>;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:[email protected]: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-3c65f53e8a006949-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:[email protected]:53166>
>
> To: <sip:[email protected]>;tag=1b6c6a0b
>
> From: <sip:[email protected]>;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 L....
>
> 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:[email protected] T=sip:[email protected] 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=z9hG4bK3d0a.008192b2.2
>
> Via: SIP/2.0/UDP
> 192.168.193.54:53166;received=192.168.193.54;branch=z9hG4bK-d8754z-3c65f53e8a006949-1---d8754z-;rport=53166
>
> Max-Forwards: 68
>
> Route: <sip:192.168.193.75;lr=on;ftag=c757db43;nat=yes>
>
> Contact: <sip:[email protected]:4530>
>
> To: <sip:[email protected]>;tag=1b6c6a0b
>
> From: <sip:[email protected]>;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=z9hG4bK3d0a.008192b2.2
>
> Via: SIP/2.0/UDP
> 192.168.193.54:53166;received=192.168.193.54;branch=z9hG4bK-d8754z-3c65f53e8a006949-1---d8754z-;rport=53166
>
> Max-Forwards: 67
>
> Contact: <sip:[email protected]:5060>
>
> To: <sip:[email protected]>;tag=1b6c6a0b
>
> From: <sip:[email protected]>;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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
sipserver.tgz
Description: sipserver.tgz
loadbalancer.tgz
Description: loadbalancer.tgz
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
