Re: [Bayonne-devel] Bayonne2, exosip2 2.2.3pl1?

[David Sugar]

Which version of eXosip2 are you using?  We had to create a special
patched version of 2.2.3 (which later became a feature in 3.0.0, though
I have not migrated to it yet) because the stack would send a 101/dialog
entry during call setup, and this seemed to crash at least some
softphone clients (cisco and snom in particular).  Besides snom, I have
mostly tested client connections  (inbound and out) with linphone (which
had the slow rtp session start and uses older exosip code) and with
Twinkle, which also has it's own SIP implementation.  I have not tested
with x-ten yet, however.

On the service provider/service source side, I have done most of my
testing with another Bayonne server, with Broadvoice, and against an
Asterisk server.  Broadvoice in particular helped a lot to get the
authentication digest/realm code and the adpcm (g721/g726-32) encoding
working correctly.

Julien Chavanton wrote:
> Better but still not working since the script exute only to log command and
> does nothing more?
> 
> 
> bool Session::enterPickup(Event *event)
> {
>        if(event->id == ENTER_STATE)
>        {
>                offhook = true;
>                startRTP();
>                startTimer(driver->getPickupTimer());
>                return true;
>        }
>        else if(event->id == CALL_ACCEPTED)
>        {
>                setRunning();
>                // startTimer(Driver::sip.accept_timer);
>                return true;
>        }
> 
>        return false;
> }
> 
> 
> 
> -----------------------------------------------------------------------------------
> 
> 
> register.sip proxy=192.168.0.156 uri=sip:address@hidden userid=202
> secret=202 timeout=3600
> 
> slog "BREAK1 dtmf_say"
> slog "BREAK2 dtmf_say"
> slog "BREAK3 dtmf_say"
> slog "BREAK4 dtmf_say"
> slog "BREAK5 dtmf_say"
> slog "BREAK6 dtmf_say"
> 
> clear %session.digits
>        play 1
>        play 2
>        play 3
>        play o k
>        goto ::mytest
> 
> program mytest
>        slog "DTMF"
>        sleep 15
>        goto ::mytest
> 
> ^dtmf
>        string.1 %keyp
>        collect %keyp count=1
>        slog "DTMF %keyp detected"
>        play &number %keyp
>        play o k
>        goto ::mytest
> 
> -----------------------------------------------------------------------------------
> 
> 
> registration for 202 updated for 180 seconds
> sip: event 0001; cid=0, did=0, rid=2, instance=4
> registration for dtmf_say confirmed for 3600 seconds
> sip: event 0001; cid=0, did=0, rid=1, instance=3
> registration for 202 updated for 3600 seconds
> sip: event 0001; cid=0, did=0, rid=1, instance=3
> registration for 202 updated for 200 seconds
> sip: event 0001; cid=0, did=0, rid=1, instance=3
> registration for 202 confirmed for 200 seconds
> sip: event 0005; cid=1, did=2, rid=0, instance=2
> sip/0: state=idle, event=201, seq=1
> sip/0: state=pickup, event=100, seq=1
> sip/0: going active; associated with 202
> sip: event 000f; cid=1, did=2, rid=0, instance=1
> sip/0: state=pickup, event=503, seq=2
> sip/0: state=run, event=100, seq=2
> sip/0: BREAK1 dtmf_say
> sip/0: BREAK2 dtmf_say
> sip: event 0012; cid=1, did=2, rid=0, instance=5
> sip: event 0012; cid=1, did=2, rid=0, instance=1
> sip: event 0012; cid=1, did=2, rid=0, instance=5
> sip: event 0019; cid=1, did=2, rid=0, instance=2
> sip/0: closing call
> sip/0: state=run, event=209, seq=5
> 
> 
> 
> On 8/11/06, David Sugar <address@hidden> wrote:
>>
>> You received a SIP call accept, which has pickup wait for the sip driver
>> "accept" timer to expire.  While waiting for the accept timer to expire,
>> it received the additional sip events and then a close.
>>
>> Perhaps we should have an option to disable accept timer and go right to
>> the run state (by calling setRunning() instead).  This is currently
>> controlled in modules/sip/session.cpp 1176;
>>
>>        else if(event->id == CALL_ACCEPTED)
>>        {
>>                startTimer(Driver::sip.accept_timer);
>>                return true;
>>        }
>>
>> in Session::enterPickup.
>>
>> Julien Chavanton wrote:
>> > I am testing Bayonne2, the script I am calling address@hidden does
>> not
>> > start ?
>> >
>> >
>> > address@hidden bayonne2-1.5.25]# vi
>> > /usr/local/share/bayonne/scripts/dtmf_say.scr
>> >
>> >
>> ---------------------------------------------------------------------------------------------------------------
>>
>> >
>> >
>> > register.sip proxy=192.168.0.156
>> uri=sip:address@hidden
>> > secret=202 timeout=3600
>> >
>> > slog "BREAK1"
>> > slog "BREAK2"
>> > slog "BREAK3"
>> >
>> ---------------------------------------------------------------------------------------------------------------
>>
>> >
>> >
>> >
>> >
>> > registration for dtmf confirmed for 180 seconds
>> > sip: event 0001; cid=0, did=0, rid=2, instance=4
>> > registration for dtmf_say confirmed for 3600 seconds
>> > sip: event 0005; cid=1, did=2, rid=0, instance=3
>> > sip/0: state=idle, event=201, seq=1
>> > sip/0: state=pickup, event=100, seq=1
>> > sip/0: going active; associated with 202
>> > sip: event 000f; cid=1, did=2, rid=0, instance=3
>> > sip/0: state=pickup, event=503, seq=2
>> > sip: event 0012; cid=1, did=2, rid=0, instance=3 (dmtf)
>> > sip: event 0012; cid=1, did=2, rid=0, instance=4 (dmtf)
>> > sip: event 0012; cid=1, did=2, rid=0, instance=2 (dmtf)
>> > sip: event 0012; cid=1, did=2, rid=0, instance=5 (dmtf)
>> > sip: event 0012; cid=1, did=2, rid=0, instance=5 (dmtf)
>> > sip: event 0012; cid=1, did=2, rid=0, instance=4 (dmtf)
>> > sip/0: closing call
>> > sip/0: state=pickup, event=209, seq=11
>> > sip/0: state=run, event=100, seq=11
>> > sip/0: state=hangup, event=100, seq=11
>> > _______________________________________________
>> > Bayonne-devel mailing list
>> > address@hidden
>> > http://lists.gnu.org/mailman/listinfo/bayonne-devel
>>
>>
>>
> _______________________________________________
> Bayonne-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bayonne-devel