I am also evaluating VoIP trunking between two of my G3rV9's and it works great, except for one problem I have discovered. It is a little difficult to describe, so bear with me.
When I call a multi-level menu that uses multiple vectors (i.e. the choice in the first menu goes to a menu in a second vector via a go-to vector or route-to VDN step), after I make my first choice, the PBX seems to be sending the touch-tones for the VDN that was called originally (it actually sounds like the VDN + #, but my touch-tone detectors, a.k.a. my ears, are not entirely accurate). You can hear the touch tones and the PBX treats them as caller input which causes mighty confusion.
This only happens with the new IP trunks.
Any ideas?
When I call a multi-level menu that uses multiple vectors (i.e. the choice in the first menu goes to a menu in a second vector via a go-to vector or route-to VDN step), after I make my first choice, the PBX seems to be sending the touch-tones for the VDN that was called originally (it actually sounds like the VDN + #, but my touch-tone detectors, a.k.a. my ears, are not entirely accurate). You can hear the touch tones and the PBX treats them as caller input which causes mighty confusion.
This only happens with the new IP trunks.
Any ideas?