Hi everyone,

 

I am in the process of doing something very straightforward - hooking up a DID from Link2Voip into my FS instance (built from SVN Curent on Debian)

 

In an effort to only change as little as possible to get this baby to respond to a phone call, I have simply added my provider into the /conf/sip_profiles/external and also added in the extension file into /conf/dialplan/extensions

 

I am able to get the system to Register and I am also able to get an incoming call - however that is where the fun stops.

 

I hit F8 on my console and this is what I got:

 

2008-09-18 02:11:38 [INFO] mod_dialplan_xml.c:228 dialplan_hunt() Processing 6044880583->18665780244 in context public

I think I understand what is going on here - but I disagree with defaults.

 

For most users, I would expect them to do exactly what I just did - try to change as little as possble and only add files as needed.

 

So finding that the initial root of the dialplan matching happens within public.xml, I attempted to see if there was a better regex match (better than the 5551212 :) and tried ^\d{10,15}$ - basically any number between 10 and 15 digits, good for most of the planet generically. I got no matches, so I though maybe the syntax was strange and went for something simpler -  ^[0-9]{10,15}$ - still no matches. Then I brute forced it - ^(18665780244)$ - got a match! yay! - Fun stops again :(

 

Just to be sure my custom extension matcher in the /conf/dialplan/extensions did not interfere with anything, I renamed it to get it from loading.

 

here is the other fun stopper:

 

My default context starts to be processed and here is the end of it....

 

2008-09-18 02:52:29 [DEBUG] mod_dialplan_xml.c:113 parse_exten() test conditions destination_number(18665780244) =~ /^9997$/

Notice the ultra generic destination number matcher getting matched? At this point it seems there is some sort of infinite loop that would keep going until I hung up the phone. I hunt down where the matcher is getting matched and find that it is in the same folder as my custom matcher inside 99999_enum.xml

 

So at this point, I go ahead and add back in my custom extension file - I get the same result - what the hell? why is my matcher not getting fired? - because its name is "link2voip.xml" which comes AFTER 99999:

 

-rw-r--r-- 1 root root 373 2008-09-18 01:27 00_pizza_demo.xml

 

I then rename it so it comes up sooner:

 

-rw-r--r-- 1 root root 177 2008-09-18 03:01 00_link2voip.xml

 

Tada! I get my wish and I can now route to where I want to! Now if I can only get the voice mail app to think I am actually saying something - I think I need to route to the echo app to see what I am saying :)

 

2008-09-18 03:08:28 [DEBUG] mod_dialplan_xml.c:113 parse_exten() test conditions destination_number(18665780244) =~ /^9996$/

 

So as a Recap, here is what I would like to have changed if possible:

Thanks for listening!

Christian

 

P.S. I originally tried this out on Windows and instead of my destination number getting set correctly, the destination number kept coming back as the username I used to log in with. Is this a known issue or shall I debug?