Paulo Scardine wrote:
> Steve Underwood escreveu:
>
>> Hi Paulo,
>>
>> The 1 or 0 should be the first dialed digit. Perhaps the other end does
>> not accept number beginning with a 1? In the working case the other end
>> asks for the ANI digits after the category. In the failed case it asks
>> for the dialed digits. However Unicall doesn't respond. Is that because
>> its in one of these "time out to end the digits" modes.
>>
>> It looks like the far end of these two E1s behaves differently. Can you
>> swap them over for a test, or is this a heavy production setup? Also,
>> can you send me the software versions you are using, and the Unicall
>> config files.
>>
>> Steve
>>
>>
> Thanks Steve, I figured out the problem, it wasn't callweavers fault.
>
> Embratel (the telco) was blocking dialout on all channels but UniCall/1,
> and this channel wasn't being charged - they do this for testing when
> installing the trunk. The tech guy forgot to switch it to normal
> operation and callweaver starts dialing from the last channels when
> Dial(UniCall/g1/${EXTEN}), so I was never dialing through channel 1.
>
> I'm so lame, so dumb, 3 weeks recompiling everything, beating the head
> against the wall...
>
>
They seem to have a rather strange way of blocking outgoing calls. Most
switches simply won't respond when you seize they line. They actually
ran through the early stages of the call.
Nice logo by the way. I thought your first submission looked too much
like a bird in a batman hood and cape. As things progressed through a
few revisions that completely changed, and I think everyone involved is
very happy with the final version. I think the bird has a nice
irreverent look now - the sort who would poo on the competition without
hesitation. :-)
Steve
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
