nope but it cant be too hard.. what does the sip.conf (and related support files) entry look like on your freepbx box for voip innovations?

First question, did you set up your MTE ip address as an endpoint in their portal? Also, what problems are you having?

well this is the sip_custom.conf ----- on the free pbx machine

; OpenSip
[opensips]
type=friend
host=72.37.220.98
context=a2billing-did
insecure=port,invite
qualify=yes
externrefresh=60
deny=0.0.0.0/0.0.0.0
permit=72.37.220.98/255.255.255.0

*******************************************
this is the sip.conf on the mte

type=peer
host=64.136.174.30
allow=ulaw
disallow=all
nat=never
canreinvite=no
dtmfmode=rfc2833

type=friend
host=64.136.174.30
allow=ulaw
disallow=all
context=from-pstn
insecure=very
[VoIP-Innovations]
qualify=yes
nat=no
;=description=VoIP Innovations US Carrier
host=64.136.174.30
dtmfmode=rfc2833
context=from-outside
type=friend
insecure=very
canreinvite=no
disallow=all
allow=ulaw

the end point is set up for our machine

i did some testing with VoIP innovations and they said that it looked like the call was getting thru to us but it looked like we were not accepting it

ok for starters you cant have 3 settings with the same ip for a host..

delete all 3 from the gui, verify theyre all gone in the file..

start over..

the type is peer not friend (set to outbound in the gui)

then when you add insecure set it as insecure=port,invite

that is what thirdlane put in there when i set up the trunk

there is only one trunk total

*************************
this is sip.conf after i remove the one trunk

type=peer
host=64.136.174.30
allow=ulaw
disallow=all
nat=never
canreinvite=no
dtmfmode=rfc2833

type=friend
host=64.136.174.30
allow=ulaw
disallow=all
context=from-pstn
insecure=very

then delete that shit.. you cant have those declarations without a channel associated. [something]

does this look better

[VoIP-Innovations]
qualify=yes
nat=no
;=description=VoIP-Innovations US Out
host=64.136.174.30
dtmfmode=rfc2833
context=from-outside
type=peer
insecure=port,invite
canreinvite=no
disallow=all
allow=ulaw

so it sounds like i need an entry for in and out?

no, peers can accept calls when you use insecure=port,invite it matches the host= ip address to the inbound call to know its voipinnovations to use for the configs.

type=user REQUIRES proxy authentication (login) to receive a call

but where does type=user get put

i think i am going to need to call in and get support started

type=user doesnt get defined AT ALL if your trying to do trusted ip.

as far as support have your credit card ready and one of our sales agents can assist in charging a block of hours .