Just started playing with SIP/URI and ENUM. I havn't found much in the way of installation documentation (if it doesn't exist I will happily jot something down). Can someone please scan thru the steps I followed and let me know if I missed something:
Questions:
- ENUMplus Module install was very straight forward, got 0.2.3 set up with zero issues. Registered and got API from enumplus.org
- I manually created an ENUM trunk with appropriate dial rules no problem. There is nothing much to configure here, does the FreePBX ENUM trunk just "know" that it is using the enumplus module for lookups?
- My PBX is not visible to the 'net, so I have created a personal SIP/URI using voip.ms and redirected it to my voip.ms DID. I have confirmed that this is working via a softphone.
- Registered two of my DID's with my new enumplus.org account, verified the numbers via the callback feature and verified that the SIP/URI is working properly.
*edit* (Using Asterisk 1.4 and FreePBX 2.6)
- What happens with my DID registrations on enumplus.org? Do those entries get shared with other enum lookup directories (e164.arpa, e164.org, e164.info, enum.org, etc.)?
- I have successfully tested my new ENUM outbound route by dialing some ENUM test numbers listed on voip-info.org and I got the "ENUM lookup successful" blurb then the outbound connection. If I dial one of my own DID's registered with enumplus.org, I get the "ENUM lookup successful" but immediately get "All circuits are busy". Is it possible to initiate and recieve the same ENUM call on the same PBX?
For testing I have created an outbound route that is dedicated to my own extension. All my dialed numbers go to this outbound route which has ENUM as the first trunk then other conventional trunks after. If I dial a number with a successful ENUM lookup, call is routed via the URI and all is well. Most calls I make, of course, do not have an ENUM lookup and I would assume that the call would just pass over the ENUM trunk and go to the next defined trunk in this outbound route. That is not the case however, it seems like if the ENUM lookup fails the call will go out using another trunk, possibly via another outbound route. Anybody know what's going on here?
Lorne

Link up your team and customers Phone System
Live Chat
Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.