Page 1 of 1
Ring Issue
Posted:
Mon Jan 10, 2011 11:13 am
by gmcust3
I was using tToR in Vnow 1.3 and I used to get Ring while dialing Manually
But In Current GoAutoDial , I don't Hear that.
Posted:
Mon Jan 10, 2011 4:22 pm
by gardo
Most ring issues on manual calls are carrier dependent if you're using VoIP. Most carriers that do LCRs (least cost routing) often don't have the ringing sound when you're dlaling manually (got lost somewhere among the carriers).
Posted:
Mon Jan 10, 2011 6:22 pm
by williamconley
in a limited way you can use the loopback dialplan to provide ringing, but it adds load to your dialer (actually makes another call!).
did you change providers when you changed to the new system? or is this a difference between asterisk 1.2 and asterisk 1.4?
Posted:
Mon Jan 10, 2011 9:50 pm
by gmcust3
Only Change looks like is Asterisk version.
Posted:
Mon Jan 10, 2011 10:26 pm
by williamconley
and you did try "r" as opposed to "R"
http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial
•R: Indicate ringing to the calling party when the called party indicates ringing, pass no audio until answered. This is available only if you are using kapejod's Bristuff.
•r: Generate a ringing tone for the calling party, passing no audio from the called channel(s) until one answers. Without this option, Asterisk will generate ring tones automatically where it is appropriate to do so; however, "r" will force Asterisk to generate ring tones, even if it is not appropriate. For example, if you used this option to force ringing but the line was busy the user would hear "RING RIBEEP BEEP BEEP" (thank you tzanger), which is potentially confusing and/or unprofessional. However, the option is necessary in a couple of places. For example, when you're dialing multiple channels, call progress information is not consistantly passed back. Look at Progress(), the progressinband setting in sip.conf or Ringing() if you would like to avoid the use of 'r' but have issues with the ringback behaviour of Dial().
Is bristuff installed?
Posted:
Tue Jan 11, 2011 12:03 am
by gmcust3
No, Its Not.
But how come Earlier It used to work ?
Due to Difference in Asterisk Version ?
Tried tTor , But No change.
Posted:
Tue Jan 11, 2011 10:48 am
by williamconley
maybe the old system had bristuff
Posted:
Tue Jan 11, 2011 10:02 pm
by gmcust3
Want me to Install bristuff and Try ?
What Others saying using 1.4 asterisk version ?
Posted:
Wed Jan 12, 2011 11:15 am
by williamconley
I think you should. Shouldn't hurt and may resolve your issue. I've noticed this same complaint a few times recently, but none as detailed as yours, so you may have the solution. Please post back one way or the other!
Posted:
Wed Jan 12, 2011 11:25 am
by gmcust3
Looking at
http://junghanns.net/downloads/?C=M;O=D
But which One to Download ?
Posted:
Wed Jan 12, 2011 11:36 am
by williamconley
Posted:
Wed Jan 12, 2011 4:51 pm
by gardo
What number are you trying to call that doesn't ring? Is it a US number? I might be able to test it with our carrier and see if the results are different.
Posted:
Wed Jan 12, 2011 5:50 pm
by williamconley
it just doesn't generate a ring tone for his agents (and the old one DID). We're investigating Bristuff as the notes state that Bristuff is required for "-R" to work.
Posted:
Fri Jan 28, 2011 4:43 pm
by lowno
So ironic. I just setup a current goautodial system and was using the lowercase r whcich did not produce a ring sound. Changed it to an uppercase R and now I get the ring sound.
I have my vicidial configured to a trixbox via IAX, the trixbox does the transcoding to g729.
Posted:
Fri Jan 28, 2011 4:51 pm
by williamconley
Good to know, so GoAutoDial provides Bristuff by default. You didn't ADD Bristuff did you? (and can you CHECk to see if you, indeed, have bristuff? that would be helpful in case Gardo doesn't pop back on and verify it ...)