[Bayonne-devel] Some Asterisk oddities with Bayonne/exosip SIP registration...

[David Sugar]

I have finally had a chance to try registering Bayonne with an asterisk 
server (sip) rather than partysip or ser.  For Asterisk I have a simple 
sip.conf for it:

[290]
username=290
type=friend
secret=testing
record_out=On-Demand
record_in=On-Demand
qualify=no
port=5060
nat=never
host=dynamic
dtmfmode=info
context=from-internal
canreinvite=no
callerid="Spot Testing" <290>

From Bayonne I have spotplay.scr:

 register.sip uri=sip:address@hidden proxy=192.168.1.95 \
 userid=290 secret=testing
        play &number 123
        sleep 500ms
        play &number 123
        exit

^2
        echo "interrupt"
        exit

This could of course also be put into a ~/.bayonnerc for testing:

[sip]
proxy = 192.168.1.95
userid = 290
secret = testing

And I set the timeout to 1 minute (I have also since fixed Bayonne's sip 
registration stuff to use seconds, not minutes...).  This was so I could 
see what happens during refreshs without having to wait very long...

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...).  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....

dyfet.vcf
Description: Vcard