[Spce-user] "100 Trying" from load balancer

Klaus Darilion klaus.mailinglists at pernau.at
Tue May 22 06:11:20 EDT 2012


Hi!

I just started playing with sip:providerCE 2.5 and I wonder why the load 
balancer sends "100 Trying"? As it relays stateless, it should not 
respond with "100 Trying" as this stops retransmissions and dropped 
packets (e.g. between LB and backend servers) will not resent.

see trace below

regards
Klaus



U 2012/05/22 11:50:05.713820 55.44.33.3:54860 -> 55.44.32.175:5060
INVITE sip:01505641636 at sipprovider.mydomain.com SIP/2.0
Via: SIP/2.0/UDP 
10.10.0.51:54860;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:sipmausi001 at 10.10.0.51:54860>
To: "01505641636"<sip:01505641636 at sipprovider.mydomain.com>
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, 
SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 1102q stamp 51814
Content-Length: 259

v=0
o=- 3 2 IN IP4 10.10.0.51
s=CounterPath eyeBeam 1.5
c=IN IP4 10.10.0.51
t=0 0
m=audio 61932 RTP/AVP 107 0 8 18 101
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

#
U 2012/05/22 11:50:05.714321 55.44.32.175:5060 -> 55.44.33.3:54860
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
10.10.0.51:54860;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860;received=55.44.33.3
To: "01505641636"<sip:01505641636 at sipprovider.mydomain.com>
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Server: Sipwise NGCP LB 2.X
Content-Length: 0


#
U 2012/05/22 11:50:05.714652 127.0.0.1:5060 -> 127.0.0.1:5062
INVITE sip:01505641636 at sipprovider.mydomain.com SIP/2.0
Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=9b22bf78;nat=yes;ngcplb=yes>
Record-Route: 
<sip:55.44.32.175;r2=on;lr=on;ftag=9b22bf78;nat=yes;ngcplb=yes>
Via: SIP/2.0/UDP 
127.0.0.1;branch=z9hG4bKf795.a5743719f4a20aa617e0893d13f52e0e.0
Via: SIP/2.0/UDP 
10.10.0.51:54860;received=55.44.33.3;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860
Max-Forwards: 69
Contact: <sip:sipmausi001 at 10.10.0.51:54860;alias=55.44.33.3~54860~1>
To: "01505641636"<sip:01505641636 at sipprovider.mydomain.com>
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, 
SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 1102q stamp 51814
Content-Length: 305
P-NGCP-Src-Ip: 55.44.33.3
P-NGCP-Src-Port: 54860
P-NGCP-Src-Proto: udp
P-NGCP-Src-Af: 4
P-NGCP-Src-Nat: 1

v=0
o=- 3 2 IN IP4 10.10.0.51
s=CounterPath eyeBeam 1.5
c=IN IP4 55.44.33.3
t=0 0
m=audio 61932 RTP/AVP 107 0 8 18 101
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
a=oldmediaip:10.10.0.51

#
U 2012/05/22 11:50:05.714761 127.0.0.1:5062 -> 127.0.0.1:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
127.0.0.1;branch=z9hG4bKf795.a5743719f4a20aa617e0893d13f52e0e.0;rport=5060
Via: SIP/2.0/UDP 
10.10.0.51:54860;received=55.44.33.3;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860
To: "01505641636"<sip:01505641636 at sipprovider.mydomain.com>
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0


#
U 2012/05/22 11:50:05.715524 55.44.32.175:5060 -> 55.44.33.3:54860
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
10.10.0.51:54860;received=55.44.33.3;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860
To: "01505641636"<sip:01505641636 at sipprovider.mydomain.com>
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0


#
U 2012/05/22 11:50:05.716739 127.0.0.1:5062 -> 127.0.0.1:5060
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 
127.0.0.1;branch=z9hG4bKf795.a5743719f4a20aa617e0893d13f52e0e.0;rport=5060
Via: SIP/2.0/UDP 
10.10.0.51:54860;received=55.44.33.3;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860
To: 
"01505641636"<sip:01505641636 at sipprovider.mydomain.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.63ad
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Proxy-Authenticate: Digest realm="sipprovider.mydomain.com", 
nonce="T7tieE+7YUxy9EoHF2lQxaMfMj8MVs3L"
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0


#
U 2012/05/22 11:50:05.716896 55.44.32.175:5060 -> 55.44.33.3:54860
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 
10.10.0.51:54860;received=55.44.33.3;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport=54860
To: 
"01505641636"<sip:01505641636 at sipprovider.mydomain.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.63ad
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 INVITE
Proxy-Authenticate: Digest realm="sipprovider.mydomain.com", 
nonce="T7tieE+7YUxy9EoHF2lQxaMfMj8MVs3L"
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0


#
U 2012/05/22 11:50:05.746549 55.44.33.3:54860 -> 55.44.32.175:5060
ACK sip:01505641636 at sipprovider.mydomain.com SIP/2.0
Via: SIP/2.0/UDP 
10.10.0.51:54860;branch=z9hG4bK-d8754z-88539b2b34142a28-1---d8754z-;rport
To: 
"01505641636"<sip:01505641636 at sipprovider.mydomain.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.63ad
From: <sip:sipmausi001 at sipprovider.mydomain.com>;tag=9b22bf78
Call-ID: MjJjNTMxMDkwYmE3ZTY3MWVjNGJmYWJiZjczMjBlNmQ.
CSeq: 1 ACK
Content-Length: 0




More information about the Spce-user mailing list