Page 1 of 1

I can hear voice, but I'm not heard

PostPosted: Thu Dec 06, 2007 1:53 am
by ramonvel
Hi Guys,

I got this problem when I place a call: I can hear the voice, but the other person doesn't hear me. On the CLI I noticed an issue with different codecs, but I don't know if that's the problem.

-- Accepting AUTHENTICATED call from 172.16.1.75:
> requested format = ilbc,
> requested prefs = (),
> actual format = ulaw,
> host prefs = (ulaw|alaw|gsm),
> priority = mine
-- Executing AGI("IAX2/e101-6", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing SetCallerID("IAX2/e101-6", "3867181811") in new stack
-- Executing Dial("IAX2/e101-6", "IAX2/from-dac/3866107346|55|o") in new stack
-- Called from-dac/3866107346
-- Call accepted by 82.165.186.90 (format ilbc)
-- Format for call is ilbc
-- IAX2/from-dac-16385 is making progress passing it to IAX2/e101-6
-- IAX2/from-dac-16385 answered IAX2/e101-6
-- Attempting native bridge of IAX2/e101-6 and IAX2/from-dac-16385
-- Operating with different codecs 4[0x4 (ulaw)] 1024[0x400 (ilbc)] , can't native bridge...
-- Hungup 'IAX2/from-dac-16385'
== Spawn extension (default, 913866107346, 3) exited non-zero on 'IAX2/e101-6'
-- Executing DeadAGI("IAX2/e101-6", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing DeadAGI("IAX2/e101-6", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG----------ANSWER-----23-----6)") in new stack
-- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcause ... --23-----6) completed, returning 0
-- Hungup 'IAX2/e101-6'

In addition to this, an error came up on the screen:

data space exceeded to 82.165.186.90:4569
Dec 6 01:06:42 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:42 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:42 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569
Dec 6 01:06:43 WARNING[3871]: chan_iax2.c:3806 iax2_trunk_queue: Maximum trunk data space exceeded to 82.165.186.90:4569


There exist a patch for the second problem, but it was reported on asterisk 1.2.13 not Asterisk 1.2.24 which is what I got now. Here is the link:

http://bugs.digium.com/view.php?id=8267

I don't mind trying it, but the only "chan_iax2.c" file that I located on my box in under the asterisk source folder. So I gues, I will have to recompile again and reinstall it. Is that right?

I want to let you know that the iax.conf and extension.conf files are originally from another box that had Asterisk-1.2.23 installed. I'm not aware of any difference. Are you aware of any change?

Please, advice how can I resolve this issue? Thanks for your help.

PostPosted: Thu Dec 06, 2007 1:56 am
by ramindia
Hi

-- Operating with different codecs 4[0x4 (ulaw)] 1024[0x400 (ilbc)] , can't native bridge...
-- Hungup 'IAX2/from-dac-16385'


Looks like you have Codec negotiation problem
check the appropriate codec server side and user end.

ram

I can hear , but I'm not heard.

PostPosted: Thu Dec 06, 2007 2:16 am
by ramonvel
Hi ram,

Thanks for your quick respond. I use IDEFISK, and I have alaw, ulaw,ilbc30,gsm ( just in that order). On the server side, on iax.conf I have:
disallow = all
allow=ulaw
allow=alaw
allow=ilbc
allow=gsm

That's under general as well as under user. But no positive result. Any other recommendation?

PostPosted: Thu Dec 06, 2007 2:33 am
by ramindia
Hi

you can try both the side

Peering side and user side

allow=all

ram

hello

PostPosted: Thu Dec 06, 2007 12:18 pm
by eliasferreyra
hello

it looks like a trunk problem, and check your router ports config the cisco router make that some times i open all listen ports and it fix:-)

check your router if is cisco configure it