I would transfer to 1000 XML default for example. This is why you split inbound and outbound into two context's like you have it... but since you're sending the call into default as 10 digits I suspect it loops right back out. Also can you please not hijack threads. Click new message, input the address yourself and then send it. If you click reply, change the subject and body you're hijacking threads DO NOT DO THAT please. /b On Sep 21, 2008, at 5:05 PM, Noah Silverman wrote:
HOW CAN I TELL FS TO ROUTE A CALL TO A REGISTERED USER AS OPPOSED TO DIALING OUT???
My guess is that's its an adjustment to the "transfer" application in my public context???
Thanks,
-Noah
-----------------------------------------------------------------------------------------------------
I can call out just fine using the following in my dialplan:
<context name="default"> <extension name="Vitelity"> <condition field="destination_number" expression="^(1{0,1}\d{10}) $"> <action application="set" data="effective_caller_id_number=12223334444"/> <!--<action application="bridge" data="sofia/gateway/vitelity/$1"/
--> <action application="bridge" data="sofia/external/$1@outbound1.vitelity.net "/> </condition> </extension> </context>
<context name="public"> <extension name="inbound"> <condition field="destination_number" expression="^(3235551212)$"> <action application="transfer" data="$1 XML default"/> </condition> </extension> </context>