multiple sip profile

Joined: Fri 20 of Apr, 2007

Re: multiple sip profile

Posted:Wed 20 of Aug, 2008 (17:28 UTC)

<param name="context" value="default"/>


<param name="context" value="inter2"/>

and then

sofia profile restart inter2 reloadxml

from the FreeSWITCH CLI
Joined: Mon 23 of Aug, 2004

multiple sip profile

Posted:Tue 12 of Aug, 2008 (05:34 UTC)
Hello :

Is there anyone tested multiple sip profiles ?

>From the FAQ:
>Q: How do I assign endpoints to contexts with different sets of extensions
>Here are the different possible approaches: 
>Use 1 profile per context you want to route to (each one needs a distinct >ip:port)     

So I duplicate the sip profiles, internal , nat , external just give them another name and different ip to use .

Sofia status still the same
                    Name          Type                               Data      State
                 internal       profile   sip:mod_sofia@210.24x.x.x:5060     RUNNING (0)
                 external       profile   sip:mod_sofia@210.24x.x.x:5080     RUNNING (0)
                      nat       profile   sip:mod_sofia@210.24x.x.x:5070     RUNNING (0)
                  default         alias                           internal      ALIASED
                  ^^^^^ is this name affecting dialplan routing ?

           210.24x.x.x         alias                           internal      ALIASED
                   inter2       profile   sip:mod_sofia@210.24y.y.y:5060     RUNNING (0)
           210.24y.y.y         alias                             inter2      ALIASED
                 outbound         alias                           external      ALIASED

FYI: setting files
sip profiles use the default config , and modify the correspoding parameter
profile name , context , domain 
[root@localhost sip_profiles]# ls -F
./  ../  external/  external.xml  inter2.xml  internal/  internal.xml  nat/  nat2.xml  nat.xml
<!-- -->
<profile name="inter2" domain="210.24x.x.x">
  <!--aliases are other names that will work as a valid profile name for this profile-->
    <alias name="210.24x.x.x"/>
    <alias name="inter2"/>

[root@localhost dialplan]# ls -F
./   default.xml     default.xml.old         extensions/   inter2.xml
../   default.xml.simpl-test  features.xml  public.xml

I also duplicate another pub2.xml for dialplan routing.

freeswitch@localhost> sofia_contact 1526@210.24x.x.x
API CALL [sofia_contact(1526@210.24x.x.x)] output:

freeswitch@localhost> 2008-08-12 13:31:58 [NOTICE] switch_channel.c:533 switch_channel_set_name() New Channel sofia/inter2/1526@ [9b9ae75d-142d-4931-956f-c6624c2d61d6]
2008-08-12 13:31:58 [INFO] mod_dialplan_xml.c:222 dialplan_hunt() Processing 1526->1527@default
                                                                                                                                    ^^^^^^^ why always go to "default" context , not the "inter2" ?

2008-08-12 13:31:58 [WARNING] switch_ivr_originate.c:539 switch_ivr_originate() No origination URL specified!

Please advise !!