Presence on dual ethernet NIC PBX

Status
Not open for further replies.

One

New Member
Feb 25, 2020
5
0
1
39
Hi,
Could you please help me configuring an instance of FS with two ethernet NIC connected to two different networks.
Networks have no routing one another and there is just pbx standing in the midle; reaching directly both of the networks.
I've tried to duplicate the internal profile, but the presence is not shared correctly between the old and the new profile.
In this scenario, when I have an extension registered to both profiles at the same time, BLF presence is not shared. If for example I answer from a device connected to one profile (and there is the same exten on another device in the second profile which is avalable and not busy), the BLF lamp stutus doesn’t stay solid red, but it becomes green in a while.

Profile internal (MASTER, eth0):
<param name="manage-presence" value="true"/>
<param name="send-presence-on-register" value="true"/>
<param name="presence-probe-on-register" value="true"/>
<param name="presence-proto-lookup" value="true"/>
<param name="manage-shared-appearance" value="true"/>
<param name="dbname" value="share_presence"/>

Profile internal-nic2 (SLAVE, eth1):
<param name="manage-presence" value="passive"/>
<param name="manage-shared-appearance" value="true"/>
<param name="dbname" value="share_presence"/>


Best regards
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,498
413
83
To use multiple SIP profiles, you need to enable dial_string in the Domain section of Default Settings. You may also need to run app_defaults from the upgrade page after making the change.
 

One

New Member
Feb 25, 2020
5
0
1
39
I use this dial_string but the problem remains: {sip_invite_domain=${dialed_domain},leg_timeout=${call_timeout},presence_id=${dialed_user}@${dialed_domain}}${sofia_contact(*/${dialed_user}@${dialed_domain})}
It's correct?
 

One

New Member
Feb 25, 2020
5
0
1
39
An example of my scenario is:

profile internal:
- yealink t40 (phone1) with ext 512
- yealink t46 (phone3) with ext 511 and a dss key (512 is the first blf)
- yealink t40 (phone4) with ext 513

profile internal-nic2:
- yealink t40 (phone2) with ext 512

1 - The ext 513 call the ext 512
2 - One of the two devices that are registered with the ext 512 answer the call
3 - FS notify to the ext 511 that the ext 512 is busy
4 - the other device registered with the ext 512 send the hangup (lose race)
5 - FS notify to the ext 511 that the ext 512 is available again (even if It’s busy)
6 - the blf of the ext 512 in the dss key is green even if it should be red

Is this scenario something related to the shared line appearance? I can test that if that’s the case.
 
Status
Not open for further replies.