See default config it lsets you do that.
Use the variables to store two versions of the callerid then set it
depending on if its outside or inside... its rather easy to do.
/b
On Nov 23, 2009, at 11:50 AM, Jonas Gauffin wrote:
Ok. It would be a nice feature if outbound_caller_id was used by
Ok. It would be a nice feature if outbound_caller_id was used by freeswitch.
I do quite often bridge to both internal and external destinations in the
same bridge command (as in "sofia/internal/5530,sofia/internal/
070123...@sipgw2..se). This forces me to always use complete phone
numbers in th
outbound_caller_id is a made up variable that is used in the defaults
that are used in the examples only.
/b
On Nov 23, 2009, at 11:24 AM, Jonas Gauffin wrote:
Ok. Found the problem. I had started using "sofia/outbound/xxx...@sipgw2..se
" as bridge destination to try to get outbound_cal
Ok. Found the problem. I had started using "sofia/outbound/
xxx...@sipgw2..se" as bridge destination to try to get
outbound_caller_id_name/outbound_caller_id_number working.
It works if I use the correct profile name, "sofia/internal/
xxx...@sipgw2..se"
When do FS use outbound_caller_id i
You set the ext-rtp-ip on the profile the phones talk too... but you
shouldn't be doing that.
/b
On Nov 23, 2009, at 11:08 AM, Jonas Gauffin wrote:
> Hello
>
> I got the following setup: Phones -> FreeSwitch -> NAT -> Internet -
> > Gateway
>
> And I'm struggling to get NAT working properly.
Hello
I got the following setup: Phones -> FreeSwitch -> NAT -> Internet ->
Gateway
And I'm struggling to get NAT working properly. I'm running freeswitch with
the "-nonat" option and have tried different ext-rtp-ip/ext-sip-ip
combinations in external/internal profiles.
The From header seems to b
