Trixbox is only used as the client to simulate what we already saw
happening with a customer.
I don't think the fact that we used a Trixbox on the client side has
anything to do with the problem on the server side which is not using
Trixbox.
The on the server side Asterisk only sees the Trixbox
On 16 Jul 2006, at 19:00, voiplist wrote:
Trixbox is only used as the client to simulate what we already saw
happening with a customer.
I don't think the fact that we used a Trixbox on the client side has
anything to do with the problem on the server side which is not using
Trixbox.
The on
Actually, at this point this info was more for the community as a
whole. We don't need to fix this now because the account code is right
and that's what is important.
On 7/16/06, Tim Panton [EMAIL PROTECTED] wrote:
On 16 Jul 2006, at 19:00, voiplist wrote:
Trixbox is only used as the
After further testing, here is what we found..
The account code was actually right after all, what made us think it
was incorrect was the fact that * was reporting the wrong channel for
the call.
For example we may have a call from iaxuser1 which comes in with the
correct account code but it
On 15 Jul 2006, at 17:24, voiplist wrote:
After further testing, here is what we found..
The account code was actually right after all, what made us think it
was incorrect was the fact that * was reporting the wrong channel for
the call.
Test 2:
We turned off the softphones mentioned
On 7/15/06, Tim Panton [EMAIL PROTECTED] wrote:
On 15 Jul 2006, at 17:24, voiplist wrote:
After further testing, here is what we found..
The account code was actually right after all, what made us think it
was incorrect was the fact that * was reporting the wrong channel for
the call.
On 15 Jul 2006, at 19:26, voiplist wrote:
On 7/15/06, Tim Panton [EMAIL PROTECTED] wrote:
On 15 Jul 2006, at 17:24, voiplist wrote:
After further testing, here is what we found..
The account code was actually right after all, what made us
think it
was incorrect was the fact that * was
Anyone have any thoughts on this?
On 7/13/06, voiplist [EMAIL PROTECTED] wrote:
We have a situation where the wrong account code is being passed from
Asterisk to our AGI and then on into the accountcode field in the CDR.
Here is the situation, best I can explain it..
We have 3 user records in
Sounds to me that the incoming call is providing the wrong userid/password.
voiplist wrote:
Anyone have any thoughts on this?
On 7/13/06, voiplist [EMAIL PROTECTED] wrote:
We have a situation where the wrong account code is being passed from
Asterisk to our AGI and then on into the
I wish it were that simple..
We see the username coming in, it's in the channel etc..
We see the call come into one account and we see * set an account code
for another account.. Really..
It seems that it has something to do with the fact that accounts
registering from the same IP get mixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
voiplist wrote:
I wish it were that simple..
We see the username coming in, it's in the channel etc..
We see the call come into one account and we see * set an account code
for another account.. Really..
It seems that it has something to do
11 matches
Mail list logo
