RE: [Bayonne-devel] Abusive CCEV_RESTART

[Julien Chavanton]

I did also comment the whole block of code since I do not want to issue several unnecessary cc_waitcall()

 

/*

                if(isdn)

                {

                        slog(Slog::levelDebug) << script << ": isdn restart" << endl;

                        HOLD("isdn restart")

                        chk = 1;

                        //chk = cc_Restart(tsdev, EV_ASYNC);

                        RELEASE

                        if(chk < 0)

                                putISDNError("cc_Restart");

                        slog(Slog::levelDebug) << script << ": isdn waiting" << endl;

                        _disconnecting = false;

                        HOLD("isdn waitcall")

                        chk = cc_WaitCall(tsdev, &lcrn, &wtcall, -1, EV_ASYNC);

                        RELEASE

                        if(chk < 0)

                                putISDNError("cc_WaitCall");

                }

*/

 

---

From: Julien Chavanton
Sent: December 1, 2004 10:00 PM
To: Julien Chavanton; address@hidden
Subject: RE: [Bayonne-devel] Abusive CCEV_RESTART

 

I did modify idle.cpp to avoid unnecessary cc_restart() also I did switch to ni2

Apparently Dialogic dms & nt1 firmware are obsolete and can result in blocked port with some new switch,

Let’s see what I will get, seam to work fine right now.

 

Julien

 

 

[Genload - ID 0] /* Dual T1/E1 HD */

ParameterFile=ni2.prm

ParameterFile2=ni2.prm

ISDNProtocol=ni2

ISDNProtocol2=ni2

 

 

 

slog(Slog::levelDebug) << script << ": setup waiting" << endl;

                if(isdn)

                {

                        slog(Slog::levelDebug) << script << ": isdn restart" << endl;

                        HOLD("isdn restart")

                        chk = 1;

                        //chk = cc_Restart(tsdev, EV_ASYNC);

                        RELEASE

                        if(chk < 0)

                                putISDNError("cc_Restart");

                        slog(Slog::levelDebug) << script << ": isdn waiting" << endl;

                        _disconnecting = false;

                        HOLD("isdn waitcall")

                        chk = cc_WaitCall(tsdev, &lcrn, &wtcall, -1, EV_ASYNC);

                        RELEASE

                        if(chk < 0)

                                putISDNError("cc_WaitCall");

                }

 

---

From: address@hidden [mailto:address@hidden On Behalf Of Julien Chavanton
Sent: December 1, 2004 8:26 PM
To: address@hidden
Subject: [Bayonne-devel] Abusive CCEV_RESTART

 

Something strange I have found with Dialogic drivers, (I think Globalcall as the same behavior)

 

I have activated dialogic event logging and

It seem the drivers are making cc_Restart after every exit command ?

More importantly as you can see when there is a join cc_restart is issued before disconnection in the following example I do not see the “481 CCEV_DISCONNECTED”.

I guess this behavior may cause problem since the other ISDN switch probably do not like this way of doing things.

And Dialogic say we should use cc_Restart only when trunk error where detected?

 

Dec  1 20:06:34 BAY-MTL3 bayonne: 79 CCEV_OFFERED

Dec  1 20:06:34 BAY-MTL3 bayonne: dx(37): index(37): * INDEX:pstn:236741918 *

Dec  1 20:06:35 BAY-MTL3 bayonne: dx(37): index(37): *** INDEX PORT:pstn:236741918 SCRIPT: noservice ***

Dec  1 20:06:36 BAY-MTL3 bayonne: 481 CCEV_CONNECTED

Dec  1 20:06:36 BAY-MTL3 bayonne: dx(37): noservice(37): *** EVENT *** childstatus:

Dec  1 20:06:36 BAY-MTL3 bayonne: dx(238): transfer(238): *** EVENT ***

Dec  1 20:06:40 BAY-MTL3 bayonne: 79 CCEV_DISCONNECTED

Dec  1 20:06:40 BAY-MTL3 bayonne: dx(238): transfer(238): *** ERROR ***

Dec  1 20:06:40 BAY-MTL3 bayonne: dx(238): transfer(238): join-parted

Dec  1 20:06:41 BAY-MTL3 bayonne: 481 CCEV_RESTART

Dec  1 20:06:41 BAY-MTL3 bayonne: dx(37): index::acctstop(37): *** INDEX HANGUP ***

Dec  1 20:06:42 BAY-MTL3 bayonne: 79 CCEV_RESTART

 

 

The cc_Restart( ) function resets the channel to NULL state. This function typically is used after the recovery of trunk errors or alarm conditions, or when the application needs to reset the channel to NULL state.

 

Any comment would be appreciated.

 

Julien