I am now able to make successful sip inbound call to Bayonne2 with
linphone.
Not sure what was my problem but I have isolated server process on
dedicated servers to avoid port conflict.
I have build my lab environment I have 2 Debian Sarge servers one for
partysip and on for Bayonne2 and a fedora core5 with linphone.
All running in (vmware) on my dual Xeon workstation with 2GB of ram, at
least I found a way to use this computer processing power.
Julien
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
g] On Behalf Of David Sugar
Sent: August 11, 2006 5:03 PM
To: Julien Chavanton
Cc: [email protected]
Subject: Re: [Bayonne-devel] Bayonne2 does not start the script
Bayonne received an exosip event "19" (hex) in dialog the middle of the
call from the remote side, which is what generated the "closing call"
message, and then disconnects. This is an EXOSIP_CALL_CLOSED, which is
presumably generated from receipt of a BYE or terminate message. It
would probably help to look at the session with wireshark.
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:[EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
does
not
start ?
[EMAIL PROTECTED] bayonne2-1.5.25]# vi
/usr/local/share/bayonne/scripts/dtmf_say.scr
------------------------------------------------------------------------
---------------------------------------
register.sip proxy=192.168.0.156
uri=sip:[EMAIL PROTECTED]
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
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
