Hi,

thanks to everybody's help on the list I managed to get callweaver work 
now for my configuration - at least as well as my asterisk was running 
before.

I have a problem that has been bothering me for the last year or so and 
which I was hoping would disappear with callweaver. I have absolutely no 
idea where it could come from:

Situation:
==========
I dial out via an internal ISDN phone connected to a HFC-S ISDN card 
running in NT mode with chan_misdn. To dial out I use SIP (i.e. in my 
case voipstunt).

The SIP connection is established without any problems, the remote 
station rings, etc - EXCEPT after about 3 ring tones or so, the 
indication on my side changes from ringing to busy. Oddly enough, the 
phone on the remote site continues ringing, can still be picked up and 
if I speak into the phone on my side (which is giving busy) the remote 
side can hear me.

To me this looked at first glance like some time-out had gone awry but I 
could not find anything in my configuration that would explain the 
phenomenon.

I have tried everything to debug this on asterisk but I have run out of 
ideas. My configuration used to work about 30 months ago but then 
developed this ailment without any changes to my system that I am aware of.


CLI output
==========
1. Following is the message I get with callweaver -dddddvvvvvgc when 
ringing starts after the connection is established:
------------
     -- Executing Dial("mISDN/1-u5", SIP/[EMAIL PROTECTED])
     -- Called [EMAIL PROTECTED]
     -- SIP/voipstunt-d73c is making progress passing it to mISDN/1-u5
Error opening Tracefile: [ /var/log/callweaver.org/misdn.log ] No such 
file or directory
     -- SIP/voipstunt-d73c is making progress passing it to mISDN/1-u5

2. When the the ringing indication changes to busy absolutely nothing 
appears in the CLI even at ridiculously high debug and verbosity level 
settings (i.e. 100)

3. When the remote phone is answered, the following message appears as 
expected suggesting nothing is wrong. But at this time, my side of the 
connection may already give me a busy indication. (If I waited long 
enough before picking up the remote side.)
----------------
     -- SIP/voipstunt-d73c answered mISDN/1-u5


Can anybody give me any hints/help on how to debug this?

Many thanks,
Arik

_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to