Home » Forums » trixbox forums » Trunks

splitting traffice between sip and iax2 trunks

rmiesner
Posts: 45
 Member Since:
2006-12-29
Submitted by rmiesner on Fri, 11/28/2008 - 11:27am.

I have 2 offices connected via sip trunk (1st trunk) and iax2 trunk (failover trunk). Office A has 2 PRI connected via sangoma card and provides dial tone to office B via sip or iax2 trunk. My question is would their be any validity in outgoing calls using sip first then iax2 if it fails and incoming call using iax2 first then sip if it fails for office B which has no local dial tone? Office B has a full T1 to Office A that is only used for the trunking of the trixboxes.

Thanks
Rusty

‹ Telco DID & CID iax_general_additional.conf ›


16again
Posts: 370
 Member Since:
2007-03-04
seems useless to me. On a
Fri, 11/28/2008 - 11:42am

seems useless to me. On a single IAX or SIP trunk you can have multiple voice channels.
I'd simply go for IAX trunk only to reduce overhead of packing audio data into IP packets



rmiesner
Posts: 45
 Member Since:
2006-12-29
i agree
Fri, 11/28/2008 - 11:48am

I think so also but I never have a problem receiving a call but have been having all circuits busy placing calls. I have talked to trixbox support and we have tweaked some things but it is still happening some and I thought it might be a capacity problem.

Rusty



SkykingOH
Posts: 7292
 Member Since:
2007-12-17
You sure the all circuits
Fri, 11/28/2008 - 12:31pm

You sure the all circuits busy is no a misdial? Since trixbox uses the 'all trunks busy' message any time the call is not accepted by the carrier I have found this to be a source of confusion.

--

Scott

aka "Skyking"



rmiesner
Posts: 45
 Member Since:
2006-12-29
yes
Fri, 11/28/2008 - 12:36pm

i have seen a few of these but after examining the logs it just says all circuits are busy on a correct number. it has me pulling my hair out.

rusty



SkykingOH
Posts: 7292
 Member Since:
2007-12-17
The log should say
Fri, 11/28/2008 - 2:22pm

The log should say congestion and the key is what is congested, the remote or local machine. You need to have correlating log data. Assuming you have reasonable size drives you can crank up the verbosity and debug levels in /etc/asterisk/logger.conf. Restart Asterisk afterward.

When you get the next event post the sanitized and relevant excerpts from /var/log/asterisk/full.* If it is long please use pastebin.ca

--

Scott

aka "Skyking"



rmiesner
Posts: 45
 Member Since:
2006-12-29
log files
Fri, 11/28/2008 - 2:46pm


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.