Skip to main content
G
georgeslouis
Participant
November 17, 2010
Question

Client Profile Configuration Scalability

  • November 17, 2010
  • 1 reply
  • 792 views

Hello,

In terms of configuring client SIP profiles, my understanding is that for every SIP client extension that is to call the FMG we need to create a profile configuration element in the sip.xml file. This is fine when the number of clients is small but what happens in the case of hundreds of clients? Would we have to create hundreds of profile elements in the sip.xml or is there a more dynamic way to manage this?

Furthermore, if we'd like to restrict the validity of these extensions to a certain time-frame or at least be able to change their passwords then is this something we can handle in FMG without having to modify the sip.xml and reload FMG every time a change is made? Or is this sort of logic reserved for back-end technology such as Asterisk's Dial-Plan whilst FMG configuration needs to remain as static as possible?

Thanks,

- Georges

This topic has been closed for replies.

1 reply

P
Piyush-G
Participating Frequently
November 18, 2010

Hello Georges,

   Unless we want to register the SIP device on FMG or need a profile specific call flow handling in workflow.xml, there is no need to create a sip profile for it.

   For an incoming request which doesn't have a matching profile, FMG can use a default sip profile. This functionality is particularly useful in case where FMG connects to a server through a SIP trunk.
  Default profile can be enabled by setting "EnableAutoProfile" tag to true in sip.xml.

  FMG supports HTTP API for dynamic configuration. It is possible to dynamically add/delete/modify sip profiles and save/revert the changes.

Thanks,
Piyush

G
georgeslouisAuthor
Participant
November 18, 2010

Hello Piyush,

But if we want every one of those devices to be able to call a flash client then we'd have to register those devices to the FMG, correct? Hence my concern in writing and maintaining all those profile elements.

How does a default sip profile work in authenticating an incoming registration request which doesn't have a matching profile?

Thanks,

- Georges

P
Piyush-G
Participating Frequently
November 19, 2010

Hello Georges,

   The default profile is selected, when an incoming INVITE doesn't match any profile. With default profile, the incoming INVITE is not challenged for authentication and the remote SIP device will not pre-register with FMG. This way the SIP devices can call any flashphone on FMG, provided they are configured to send INVITE request to FMG - by setting domain or proxy to FMG machine address.

  If there is a requirement to authenticate each incoming call (from SIP end), then there are 2 possibilities. If they have different username/passwords, then we need to create a separate profile for each device. Otherwise if they are configured with same username/password, then they can share one SIP profile, where doRegister is 0.

  If the SIP devices are registered with another server (i.e. they don't talk to FMG directly), then authentication can be done at that server and FMG default profile could be used for incoming calls.

Thanks,

Piyush

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices