I see what I do. When I set to 1 minute, for example, I actually
refresh every 26 seconds, so if the udp registration is lost, another
will appear before it expires. When I get the failed message, I reset
my timeout for refesh to 1, and wait for the next loop through the
refresh routine. I then send the registration yet again, and this
second time it then takes it. Thats why I get back two events. Still
odd, as it looks like it always rejects the first refresh/registration
attempt, and yet always accepts it when the very same request is
repeated a moment later.
Aymeric Moizard wrote:
Sure enough it registers. I can dial 290 from another extension, and
it calls my server and runs my script just as it should! However,
every time it refreshes, it returns to me both a fail and accept on
the registration through exosip (eXosip "1", I haven't converted to
exosip2 yet...).
If asterisk send 2 SIP messages answer to ONE request, then asterisk
should be broken!
No more info... I didn't try myself.
Aymeric
So I get both a fail and confirm event back...how very odd! Also,
according to Asterisk, it claims not to see me actively "monitoring"
my sip endpoint, though, again, it is quite able to send me calls.
So the question is which is broken (something in Bayonne, Asterisk, in
eXosip?!), and if so in what way? Is it normal to get two responses
back? Why doesn't it see me as monitoring, yet is still able to send
me calls? Asterisk could not seem to do this for my old broken bt100
once it lost track of its monitoring....
begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
adr:;;;;;;USA
email;internet:[EMAIL PROTECTED]
x-mozilla-html:FALSE
url:http://www.gnutelephony.org
version:2.1
end:vcard
_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
