Re: [Ekiga-list] Peering with SIPBroker enabled

["Bent Bagger" <bbagger gmail com>]

Maybe I should make myself a little more clearer: When I try to call
*393613 ekiga net I get a 'not found' response back. Here is the short
version of an Ethereal trace:

1   0.000000 83.73.254.57 -> 213.186.62.145 SIP/SDP Request: INVITE
sip:*393613 ekiga net, with session description
 2   0.083174 213.186.62.145 -> 83.73.254.57 SIP Status: 404 Not found
 3   0.083930 83.73.254.57 -> 213.186.62.145 SIP Request: ACK
sip:*393613 ekiga net

When I call 500 ekiga net, I am connected and get this:

 1   0.000000 83.73.254.57 -> 213.186.62.145 SIP/SDP Request: INVITE
sip:500 ekiga net, with session description
 2   0.083229 213.186.62.145 -> 83.73.254.57 SIP Status: 407 Proxy
Authentication Required
 3   0.084030 83.73.254.57 -> 213.186.62.145 SIP Request: ACK sip:500 ekiga net
 4   0.085204 83.73.254.57 -> 213.186.62.145 SIP/SDP Request: INVITE
sip:500 ekiga net, with session description
 5   0.177261 213.186.62.145 -> 83.73.254.57 SIP Status: 100 trying
-- your call is important to us
 6   0.179952 213.186.62.145 -> 83.73.254.57 SIP/SDP Status: 200 OK,
with session description
 7   0.182308 83.73.254.57 -> 213.186.62.145 SIP Request: ACK
sip:500 213 186 62 145:5080
 8   7.404837 83.73.254.57 -> 213.186.62.145 SIP Request: BYE
sip:500 213 186 62 145:5080
 9   7.482955 213.186.62.145 -> 83.73.254.57 SIP Status: 200 OK

The difference is obvious, but why??? Any help will be much appreciated.

The full traces are available if desired.

Kind regards,
Bent