Quantcast
Channel: VoIP / SIP Phones topics
Viewing all articles
Browse latest Browse all 3669

Strange BLF key behavior

$
0
0

I've set up a BLF key on extension 1005 to monitor 1001.  When a call comes into 1001 and it starts ringing the blf key on 1005 lights up solid red immediately which I believe means that 1001 is busy but not necessarally ringing.  1005 never presents the ringing popup and I cannot intercept the call by pushing the blf key which instead initiates a call to 1001 as if the call had already been answered.

 

I'm running a vvx600 on 1001 and a vvx400 on 1005.  Both have Firmware 5.7 and my pbx is a Grandstream ucm6204.

The relivent blf key settings on 1005 are:

 

 

attendant.behaviors.display.remoteCallerID.normal="1"
attendant.behaviors.display.remoteCallerID.automata="1"
attendant.behaviors.display.spontaneousCallAppearances.automata="1"
attendant.behaviors.display.spontaneousCallAppearances.normal="1"
attendant.resourceList.1.label="Main"
attendant.resourceList.1.address="1001@192.168.0.39"

feature.directedCallPickup.enabled="1"
call.directedCallPickupMethod="legacy"
call.directedCallPickupString="**"

 

I did a packet capture and I do see a SIP packet to the 1005 phone indicating <state>early</state> which suggests to me that the pbx is doing the right thing and the phone really should know that 1001 is ringing.  Here is the body of the initial SIP Notify that gets sent to 1005 when 1001 starts ringing:

<?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:1001@203.0.113.81:5060"><dialog id="1001"><state>early</state></dialog></dialog-info>

 

I don't really know at this point if I'm dealing with a phone config issue or a pbx config issue so I'd appreciate any suggestions.

 


Viewing all articles
Browse latest Browse all 3669

Trending Articles