On Mon, Jul 26, 2010 at 10:40 AM, ovvenkat <ovvenkatesan@gmail.com> wrote:

oops .. sorry peder, I was doing trial and error method and forgot to revert it back. Here is the correct one and still no luck :( .

I have created local extension 1100 and registered with freeSwitch and then added below rule into /usr/local/freeswitch/conf/dialplan/public/00_inbound_did.xml file

<include>
<extension name="public_did">
    <condition field="destination_number" expression="^(xxxyyy)$"> xxxyyy--> my PRI number
      <action application="set" data="domain_name=$${domain}"/>
      <action application="transfer" data="1100 XML default"/>
    </condition>
</extension>
</include>
Here is the link of the pastbin for fs_cli logs.

http://pastebin.freeswitch.org/13532

You're almost there. You just need to modify the regular expression in the Local_Extension dialplan entry. As Milena said, I gave explicit instructions on how to do that in my other post.

As a reminder to anyone reading this thread... When you see a log entry like this:
Dialplan: OpenZAP/1:13/1100 Action transfer(1100 enum)

It means that the dialed number did not match any expressions! It's falling back the the "last resort" extension, aka ENUM. In this user's case he added user id "1100" to his directory but he did not add "1100" to is dialplan to allow the new user's phone to be dialed. The default dialplan has the "Local_Extension" with this condition:
<condition field="destination_number" expression="^(10[01][0-9])$">

This user could do something like this to allow explicitly "1100" to be dialed:
<condition field="destination_number" expression="^(10[01][0-9]|1100)$">

OR he could add 1100 as part of a range. The follow allows 1100 to 1119 to be dialed:
<condition field="destination_number" expression="^(1[01][01][0-9])$">

Either method works - it's just a matter of whether or not you need to allow dialing to 11xx or just 1100.

Now everyone go buy the new FS book! :P
-MC