Hello,
Anyone have a working Viatalk trunk on trixbox 2.6.0.5?
I've got a working Viatalk trunk on a production machine running trix 2.0 but can't get that same trunk config to work on 2.6.0.5 (fresh install on test machine; prod machine turned off). Trunk registers with Viatalk according to the Asterisk Info page, however, I get an "all circuits are busy now, please try your call again later" msg on outbound call attempts. Inbound calls go directly (no ringing) to VM.
TIA>
-g.
Hi,
I have a Viatalk trunk working in Trixbox 2.6.0.5, although for some reason outbound CID is not working all the time. Otherwise the trunk appears to be working fine. Here are the PEER Details from the trunk settings:
bindport=5060
port=5060
bindaddr=0.0.0.0
recordhistory=yes
canreinvite=no
disallow=all
allow=ulaw&gsm
trustrpid=yes
sendrpid=yes
dtmfmode=inband
relaxdtmf=yes
realm=asterisk
type=peer
authuser=xxxxxxxxxxx
username=xxxxxxxxxx
fromuser=xxxxxxxxxxx
host=chicago-9.vtnoc.net
secret=xxxxxxxx
insecure=very
qualify=3600
nat=yes
context=from-trunk
My Trixbox is behind a NAT router (DD-WRT).
Let me know if this helps at all.
-tl
These are my settings for VIATALK as a sip trunk...Trixbox 2.x worked great but with Trixbox 2.4.x and 2.6.x my old settings didn't work...Because of the asterisk 1.4..Below are the settings which works with asterisk 1.4...
General Settings :-
Outbound Caller ID "Name" = 11 Digit DID Given By Viatalk
Maximum channels : 2
Outgoing Settings : -
Trunk Name : Viatalk
PEER Details : -
allow=ulaw
authuser=12345678900
context=from-trunk
disallow=all
dtmf=auto
dtmfmode=inband
fromdomain=chicago-1c.vtnoc.net
fromuser=12345678900
host=chicago-1c.vtnoc.net
insecure=very
qualify=yes
secret=secret
type=peer
username=12345678900
Incoming Settings :-
NOTHING NEEDED... (But you will have to create inboud route or assign direct DID to one of the extension.)
Registration :-
12345678900:secret@chicago-1c.vtnoc.net/12345678900
Does that configuration give you consistent outbound CID? It's really weird, but if I make an outbound call using X-Lite, CID is sent appropriately. On the other hand, if I use a regular phone connected to an SPA-3102 and make an outbound call, the CID shows up as OUT OF AREA. Both are set up as SIP extensions and they are configured virtually identically. So I'm really puzzled as to what is happening to CID when using the Linksys. This used to work just fine with my old Trixbox 2.0 configuration.
-tl
Turns out I took the PEER settings from a recommended set of settings in the Viatalk forums. For whatever reason, they suggest setting trustrpid=yes and sendrpid=yes, which from what I can tell let's the SIP device determine the CID if it sends the information in the SIP request. Since I want the CID to always be the DID of the Viatalk trunk, it makes no sense to set those. Setting them to no, or just leaving them out of the PEER details makes it all work just fine.
-tl
Thanks for the replies,
Yea looks like trix 2.6/* 1.4 requires different trunk settings. Got it working with this config: https://support.viatalk.com/index.php?_a=knowledgebase&_j=questio...
I just updated my existing trunk config with the "TRUNK CONFIGURATION" lines and it worked.
Also needed to allow anonymous sip calls to get inbound working.
Copyright © 2011 Fonality
Fonality and trixbox are trademarks of Fonality. Trademark Policy. Privacy Policy.
Asterisk is a trademark of Digium, Inc. Fonality and trixbox are not affiliated with, nor endorsed by Digium, Inc.
Member Since:
2006-11-23