I dont know if this only happen to me or I'm not using a configuration flag
that is document, but I have a very hard time figuring this out.
I have a customer with a SIP server represented by an FQDN configured as A
records
When my application sends a REGISTER I see from the logs:
( i change real IPs and SIP headers )
nta: selecting scheme sip
sres_cache_get(0x5163510, A, "mobile1.mysip.com.") called
sres_cache_get(0x5163510, A, "mobile1.mysip.com.") returned 4 entries
nta: for "mobile1.mysip.com" query "mobile1.mysip.com" A (cached)
nta: mobile1.voncp.com. IN A 1.2.3.4
nta(0x5166dd0): A 1.2.3.5
nta(0x5166dd0): A 1.2.3.6
nta(0x5166dd0): A 1.2.3.7
tport_tsend(0x5162ec0) tpn = udp/1.2.3.4:1/sip
tport_resolve addrinfo = 1.2.3.4:1
tport_by_addrinfo(0x5162ec0): not found by name udp/1.2.3.4:1/sip
tport_vsend(0x5162ec0): 779 bytes of 779 to udp/1.2.3.4:1
tport_vsend returned 779
send 779 bytes to udp/[1.2.3.4]:1 at 18:54:28.65:
REGISTER sip:mobile1.mysip.com SIP/2.0
Via: SIP/2.0/UDP 192.168.10.104;rport;branch=z9hG4bKeBKv0gtgt114K
Max-Forwards: 70
From: ;tag=BgcaXZpBrS77F
To:
Call-ID: d256fa75-00ad-122e-b2ac-859f8642be87
CSeq: 132930045 REGISTER
Contact: ;audio;text;mobility="mobile"
Expires: 3600
User-Agent: MyUA
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY,
REFER, UPDATE
Supported: timer, 100rel, path
Content-Length: 0
The server at 1.2.3.4 doesn't respond so Sofia-SIP send 11 ( or 10 ) retries
and timer F fires. At this time the stack switch to the next server 1.2.3.5:
nta: resent REGISTER (132930081) to udp/1.2.3.4:1/sip
tport_pend(0x5162ec0): pending 0x5173500 for udp/192.168.10.104:5060 (already 0)
nta_outgoing_timer: 1/1 resent, 0/1 tout, 0/0 term, 0/1 free
nta: timer set next to 491 ms
nta: timer F fired, timeout REGISTER (132930081)
nta(0x516b6b0): try next after timeout
tport_release(0x5162ec0): 0x5173500 by 0x516b6b0 with 0x0
tport_tsend(0x5162ec0) tpn = udp/1.2.3.5:1/sip
tport_resolve addrinfo = 1.2.3.5:1
tport_by_addrinfo(0x5162ec0): not found by name udp/1.2.3.5:1/sip
tport_vsend(0x5162ec0): 779 bytes of 779 to udp/1.2.3.5:1000
This one works OK and the server sends a respond to the client.
The problem is that the next REGISTER goes again to 1.2.3.4.
There is no mechanism that nta can remember that 1.2.3.4 is not answering and
put it at the bottom of the list and continue to use 1.2.3.5, the
last one that did respond ?
In other words, how to force the stack to use from now 1.2.3.5 and not 1.2.3.4
???
Thanks
Inca--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
