V5 BLF PSTN Line ?

[AldoLinares]

I already set up the GXP2000 for the BLF on some extensions and it's working fine, the only thing i noticed it's it gets activated only when the call its used the first time. No problem for that.

The question that i have i tried to set up on PSTN Line 10001 and dont work, maybe BLF it's only intended for Extensions, but it's possible to watch on BLF the LINES?

Thanks

 

[archie]

Yes, currently you can monitor only extention states with BLF. It will be expanded to monitor lines too, but later. But if you have 'Presense watcher' option for BLF (latest firmware of GXP has it) - you could monitor lines too, I suppose (actually, I didn't check it yet, but it should work).

 

[AldoLinares]

I try it but it gets green, but if the line it's use it continue to be green, never change color to red or something.

 

[5qg4]

Hi AldoLinares,

I also test the BLF. However, it just working. The BLF status indicator are NOT in correct status at following scenario.

Grandstream BT-200: EXT 301
Polycom IP330: EXT 341
Grandstream GXP-2000: EXT 473 (BLF console)
Our testing:
1. EXT 301 issue call to EXT 341 (Both LED inidcator for 301 and 341 are
flash in Green color)
2. EXT 341 pick up the call (Both LED inidcator for 301 and 341 are in Red
color)
3. EXT 301 hang up the call (LED inidcator for 301 in Green color, LED
inidcator for 341 in Red color)


15:34:00.984 Call::Terminate [CM503008]: Call(32): Call is terminated
15:34:00.984 Call::Terminate [CM503008]: Call(32): Call is terminated
15:33:56.046 CallLeg:nConfirmed Session 557 of leg C:32.1 is confirmed
15:33:55.890 CallCtrl:nLegConnected [CM503007]: Call(32): Device joined:
sip:[email protected]:5060
15:33:55.890 CallCtrl:nLegConnected [CM503007]: Call(32): Device joined:
sip:[email protected]:5060;transport=udp
15:33:55.875 MediaServerReporting::SetRemoteParty [MS210007] C:32.1:Answer
provided. Connection(direct): 10.1.1.19:2230(2231)
15:33:55.875 MediaServerReporting::SetRemoteParty [MS210001] C:32.2:Answer
received. RTP connection: 10.1.1.19:2230(2231)
15:33:55.875 CallLeg::setRemoteSdp Remote SDP is set for legC:32.2
15:33:54.718 Extension:rintEndpointInfo [CM505001]: Ext.341: Device info:
Device Identified: [Man: Polycom;Mod: SoundPoint IP 330;Rev: General]
Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent:
[PolycomSoundPointIP-SPIP_330-UA/2.2.0.0047] Transport: [sip:10.1.1.10:5060]
15:33:54.718 CallCtrl:nAnsweredCall [CM503002]: Call(32): Alerting
sip:[email protected]:5060
15:33:54.484 MediaServerReporting::SetRemoteParty [MS210006] C:32.2:Offer
provided. Connection(direct): 10.1.1.23:5004(5005)
15:33:54.468 CallCtrl:nSelectRouteReq [CM503004]: Call(32): Calling:
Ext:341@[Dev:sip:[email protected]:5060]
15:33:54.468 CallCtrl:nSelectRouteReq Making route(s) to
[sip:[email protected]]
15:33:54.468 MediaServerReporting::SetRemoteParty [MS210000] C:32.1:Offer
received. RTP connection: 10.1.1.23:5004(5005)
15:33:54.453 CallLeg::setRemoteSdp Remote SDP is set for legC:32.1
15:33:54.453 Extension:rintEndpointInfo [CM505001]: Ext.301: Device info:
Device Not Identified: User Agent not matched; Capabilities:[reinvite,
replaces, able-no-sdp, recvonly] UserAgent: [Grandstream BT200 1.1.5.15]
Transport: [sip:10.1.1.10:5060]
15:33:54.421 CallCtrl:nIncomingCall [CM503001]: Call(32): Incoming call
from Ext.301 to [sip:[email protected]]

Our finding is, if the caller hang up the
call first will cause the BLF status indicator in-correct stage. How about you?

 

[AldoLinares]

5qg4

My phones are showing the extensions fine, if they are in use they will be red if they are idle they are green, but if a phone since the boot up of the phone never get used the led will never be green or red.

I was asking if i can configure a PSTN Line or VOIP line to show on the BLF.

Another strange thing is that if the phone it's not used for some time (don't know how many time) the led will go off.

 

[silentfun]

i have tryed latest FW on the GXP-2020 1.1.5.15 but it is realy bad.

- BLF is like a Oracles Guess

- is some conditions when u want to change something via web interface the phone freeze

- it seems that it forget to refresh the registering at the PBX server. all other phones show register expired and then reregister but not the GXP with new firmware - when i try a call next mornig i can not without reboot

- if you use other then english language u have trouble with ÄÖÜß and so on.

- XML Applications for softbuttons don´t run

- idle/custom screen have no status bar and not all variables u need

- and the display texts are much too big. ok 1.1.4.17 was a bit small but hey this is too big now.

- sometimes it have bad timeouts so if you dial fast 12345 it only accept 12 and eat the rest and u have to type again 345 and the push send or wait 4 seconds

so i have decided to go back to 1.1.4.17 because it is stable but have no xml Appl. it run ok with V3.

so beware of GXP-2020 1.1.5.15

Andy

 

[archie]

Sorry, forgot to mention, in case of Presence watcher you CAN monitor lines, BUT it will show only whether line is registered or not. It's the limitations of "presence" event itself. When we'll implement dialog-info for lines (and it will happen quite soon) - you will be able to monitor them with "Asterisk BLF" option and it will show calling/ringing and in-a-call states too, as it does for extensions now.

 

[AldoLinares]

In the newer version of the FW of the GXP2000 they changed the name from Asterisk BLF to Busy Lamp Field

Also there is a new option:

Eventlist BLF

 

[silentfun]

Yes they changed the name but the funktion from Grandstream GXP´s is not good for productive systems because it seems the status only get Changes of the Status - and if he don´t get the change in any scenario it show you the false state until he get an other change.

very bad thing if you trust in the Status Lights

Andy