[Bayonne-devel] Abusive CCEV_RESTART

[Julien Chavanton]

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