Is there an IAX2 bug.
Added by Ken White over 13 years ago
Cannot call outbound on IAX2 trunk:
The error:
[Nov 6 14:56:05] WARNING7157 channel.c: No channel type registered for ''
[Nov 6 14:56:05] WARNING7157 app_dial.c: Unable to create channel of type '' (cause 66 - Channel not implemented)
[Nov 6 14:56:05] VERBOSE7157 logger.c: [Nov 6 14:56:05] Everyone is busy/congested at this time (1:0/0/1)
[Nov 6 14:56:05] VERBOSE[7157] logger.c: [Nov 6 14:56:05] -- Executing [91XXXXXXXXXX@default:3] Hangup("Local/91XXXXXXXXXX@default-234e,2", "") in new stack
[Nov 6 14:56:05] VERBOSE[7157] logger.c: [Nov 6 14:56:05] Spawn extension (default, 91XXXXXXXXXX, 3) exited non-zero on 'Local/91XXXXXXXXXX@default-234e,2'
[Nov 6 14:56:05] VERBOSE7157 logger.c: [Nov 6 14:56:05] -- Executing [h@default:1] DeadAGI("Local/91XXXXXXXXXX@default-234e,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----66-----CHANUNAVAIL----------") in new stack
IAX2 Carrier Setttings:
registration string:899999999:[email protected]:4569
[voiptalk]
accountcode=899999999
type=peer
trunk=yes
secret=secret
host=FQDN of carrier
disallow=all
allow=g729
context=default
File ->vicidial_iax.conf
register =>899999999:[email protected]:4569
; VICIDIAL Carrier: VTalk1 - VoipTalk
[voiptalk]
accountcode=899999999
type=peer
trunk=yes
secret=secret
host=FQDN
disallow=all
allow=g729
context=trunkinbound
Comments:
1. IAX2 port is open the firewall
2. I can use the carrier on another server to send and receive calls
Questions:
1. Does the error indicate a problem with configuration of the carrier in goautodial? Or
2. Does the error indicate a problem with connecting to the carrier?
Any help would be appreciated.
Thanks.
Ken
Replies (4)
RE: Is there an IAX2 bug.
-
Added by Demian Biscocho over 13 years ago
Please post your dialplan entry for your IAX2 carrier. Also the Asterisk CLI on the start of the call to the finish.
RE: Is there an IAX2 bug. [SOLVED]
-
Added by Ken White over 13 years ago
Thanks for the reply.
Got it going.
Had to fix the dial plan. I found it difficult to modify the matching extension in the dial plan to allow the call to be sent to the carrier with the dial prefix. ogautodial gets very antsy if you fiddle around the the match string in the dial plan
I just leave the matching string as is and add the 1 before the called number.
Ken
RE: Is there an IAX2 bug. [SOLVED]
-
Added by Ken White over 13 years ago
Ken White wrote:
Thanks for the reply.
Got it going.
Had to fix the dial plan. I found it difficult to modify the matching extension in the dial plan to allow the call to be sent to the carrier with the dial prefix. ogautodial gets very antsy if you fiddle around the the match string in the dial plan
I just leave the matching string as is and add the 1 before the called number.
Ken
PS. There is no bug.
RE: Is there an IAX2 bug.
-
Added by farijon farijon about 13 years ago
Besides being good time savers, these templates are equally useful, good orderly and elementary to use aiou