SIP.conf/fop2 users, how do you tie them up?

[silas2]

I'm sure this is staring me in the face, but I don't quite understand the relationship between the user list in fop2.cfg and Sip.conf user list/sip registrations , how do you tie them together?(they are presumably the same thing(?))

[nicolas]

Hi,

The user list in fop2.cfg is for defining extensions that you can use to log into fop2 itself.

The user must be the extension number if you want to be able to perform actions in fop2. You can use anything else too, strings, invented numbers, but in those cases you won't be able to perform actions.

There is no direct relation to sip.conf, that is up to your own asterisk configuration. The relation for fop2 is between the user number and the extension setting in a button configuration also in fop2.cfg

Example

fop2.cfg

user=100:1234:all
buttonfile=buttons.cfg

buttons.cfg

[SIP/john]
type=extension
extension=100
context=from-internal

So, as you can see, there is a relation between the user and the button. But no relation at all with your sip.conf

[silas2]

If know I must be exposing a fundamental misunderstanding, but if asterisk has all these sip calls getting 'bridged' between the registered sip phones and the outside world, doesn't fop2 somehow 'sit' on top of that to flash the lines which are active, etc, etc?

[nicolas]

I do not understand your question. You define buttons in fop2 as in the example above, it is not a fop2 user but a fop2 button.

The button definition requires the device to monitor between brackets, that is the "bond" that you are looking for with your asterisk sip.conf file.. but it is not only with that, as you can have other button types, like conferences, queues, etc..

[silas2]

Is it that the buttons bind to channels, which take the form SIP/username (=sip.conf username??)
(link to relevant documentation would be welcome if I'm overlooking the obvious)

[nicolas]

I do not understand what is your doubt:

http://www.fop2.com/documentation-confi ... uttons.php

In Asterisk you have device names, fop2 monitors those device names.. The device name depends on the channel driver. That is outside the scope of fop2 itself, is an asterisk thingy... so, sip channels in asterisk are named:

SIP/xxxxx

In sip.conf you can define a peer like

[100]

And the device name when in use in asterisk will be

SIP/100

In fop2.cfg you must use the device/channel name. Example:

SIP/100
IAX2/mary
DHADI/2

The documentation is in the link I posted above, or you can see it also in the buttons.cfg.sample included with fop2

[silas2]

Thanks, that was it.