Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » Bug - transfer call to a ringing blf
  •  
link611

Messages: 70
Karma: 0
Send a private message to this user
Hi there,

i think there is a huge bug in the transfering system of the operator with snom phones.

snom D725 with configured BLF like in this kb explained:

http://kb.kerio.com/product/kerio-operator/configuring-phone s-devices/how-to-configure-busy-lamp-field-blf-on-snom-phone s-742.html

all D725 have this configuration:
fkey9!: blf sip:17<_at_>192.168.100.10;user=phone|**
number_simultaneous_calls&: 2
call_waiting1&: visual



Now:

extension 17 receives a call over a ringing group, the phone rings.
17 is not answering the call, it still rings.

extension 27 is in a call and transfers the call to 17 over the blf (transfer -> fkey), while 17 is ringing.

-> Boom, the external caller for 17 (who is ringing) and the one (external) who is transferred from 27 are in a call together....



i created a topic on the snom helpdesk, they say it is a problem of Operator, it seems, that the Operator bridging both external calls together.


SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.100.10:5060;branch=z9hG4bK69396a25
From: "xxxxxxxx" <sip:xxxxxxx<_at_>192.168.100.10>;tag=as398ccf8c
To: <sip:17<_at_>192.168.100.125:5060>;tag=rf71equoha
Call-ID: 1351b44600e5d9846480ae0e105b3c76<_at_>192.168.100.10:5060
CSeq: 102 INVITE
User-Agent: snom725/8.7.5.35
Contact: <sip:17<_at_>192.168.100.125:5060>;reg-id=1
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
Allow-Events: talk, hold, refer, call-info
Content-Length: 0


Received from udp:192.168.100.10:5060 at May 4 14:32:28 (410 bytes):

CANCEL sip:17<_at_>192.168.100.125:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.10:5060;branch=z9hG4bK69396a25
Max-Forwards: 70
From: "xxxxxxxx" <sip:xxxxxxxxxx<_at_>192.168.100.10>;tag=as398ccf8c
To: <sip:17<_at_>192.168.100.125:5060>
Call-ID: 1351b44600e5d9846480ae0e105b3c76<_at_>192.168.100.10:5060
CSeq: 102 CANCEL
User-Agent: Asterisk PBX
Reason: SIP;cause=200;text="Call completed elsewhere"
Content-Length: 0




can you help/reproduce the problem and maybe fix this?
  •  
Filip Jenicek (Kerio)

Messages: 1075
Karma: 78
Send a private message to this user
Hi,

it sounds to me, that by hitting the blf key 17, you actually performed a call pickup of the ringing phone and transfered your call to the ringing one. Although one might not expect it, it behaves exactly how your phone is configured.

If you want, create a packet dump capturing the situation and I'll look at it to tell you exactly what happened.

Filip
  •  
link611

Messages: 70
Karma: 0
Send a private message to this user
with packet dump you mean the pcap trace function of the snom phones?
  •  
Filip Jenicek (Kerio)

Messages: 1075
Karma: 78
Send a private message to this user
A dump from Operator would be much better. There's a button on the Network screen.
  •  
link611

Messages: 70
Karma: 0
Send a private message to this user
attached.

ext 17 is the one who rings, ext 27 the one who wants to transfer a call

  • Attachment: dump.7z
    (Size: 1.46MB, Downloaded 32 times)
  •  
Filip Jenicek (Kerio)

Messages: 1075
Karma: 78
Send a private message to this user
Hi,

the inbound call to ext. 27 was answered and aprox. 15 seconds later was transfered by the snom phone to number **17.

Your snom phone's blf button is probably configured to monitor ext 17. If the extesion is idle, the phone will dial the extension number 17. If extension is ringing, the phone will dial **17 to pickup the ringing call.

Apparently, the phone does the same thing when doing a call transfer. I'm sorry, but this is not something Operator could affect.

Filip
Previous Topic: check sip trunk register status periodically
Next Topic: Forwarding calls coming from a ringing group
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Sun Jan 22 13:16:48 CET 2017

Total time taken to generate the page: 0.01040 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.