[Freeswitch-users] Fwd: Not able to do outbound call

[Michael Collins]

On Thu, Jul 22, 2010 at 6:30 AM, David Ponzone <david.ponzone at gmail.com>wrote:

> Usually, you paste that to a pastebin, and send us the URL.
> Pasting the whole log here is not really a good practice.
>
> Whatever, it's done now, so I think your issue is:
>
> 2010-07-22 16:47:27.928811 [DEBUG] mod_enum.c:204 Unable to lookup NAPTR
> record for0.0.1.1.e164.org: valid domain but no data of requested type
>
> 2010-07-22 16:47:27.928811 [INFO] switch_core_state_machine.c:142 No Route,
> Aborting
> 2010-07-22 16:47:27.928811 [DEBUG] switch_channel.c:2261 (OpenZAP/1:2/1100)
> Callstate Change RINGING -> HANGUP
> 2010-07-22 16:47:27.928811 [NOTICE] switch_core_state_machine.c:143 Hangup
> OpenZAP/1:2/1100 [CS_ROUTING] [NO_ROUTE_DESTINATION]
>
> 2 things:
> -it's unusual a call coming from TDM lands on default.xml, but I guess
> that's what you wanted
> -if it's ISDN, it's possible you only receive the last 4 digits of the DID,
> so you need to match that.
>

This is a classic case of falling back to enum because of no matching
destination number. Note this line from near the beginning of the trace:
2010-07-22 16:47:27.312160 [INFO] mod_dialplan_xml.c:331 Processing
9677012480->1100 in context default

The inbound call is looking for destination number "1100". You don't have a
dialplan entry that matches 1100 so it finally gets to the end of the
dialplan and sees this:
Dialplan: OpenZAP/1:2/1100 Regex (PASS) [enum] destination_number(1100) =~
/^(.*)$/ break=on-false
Dialplan: OpenZAP/1:2/1100 Action transfer(1100 enum)

I'm pretty sure that's not what you want. If you have a phone registered as
"1100" then the quick thing to do would be to modify the Local_Extension
regex. You can see the Local_Extension regex failing to match "1100" from
this part of your log:
Dialplan: OpenZAP/1:2/1100 Regex (FAIL) [Local_Extension]
destination_number(1100) =~ /^(10[01][0-9])$/ break=on-false

Open up conf/dialplan/default.xml and locate the "Local_Extension" entry.
Change the regex to allow 1100 to match. Either of these patterns will work:
^(1[01][01][0-9])$   (this pattern matches 1100-1119 in addition to the
default 1000-1019)
^(10[01][0-9]|1100)$   (this pattern matches 1100 specifically, in addition
to the default 1000-1019)

Hope that info helps. BTW, all this is covered in the intro article:
http://bit.ly/EpVrv

It's also covered in our new book so now that we've been nice to you, you
have to go buy it! :P
-MC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100722/433770c2/attachment-0001.html