Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » BLF with operator in the cloud (BLF cloud)
  •  
HB

Messages: 32
Karma: 0
Send a private message to this user
I'm testing kerio operator in the cloud.
1 problem.
BLF works not 100%.
Cannot transfer and call pickup !
when i transfer by hand to 201 no problem.( log 1 from snom 320)
But pressing BLF disconnected not found ( log 2 from snom 320)

log 1:
From: "203" <sip:203<_at_>xxx.xxx.xxx.xxx>;tag=5o31h5u0pv
To: <sip:201<_at_>xxx.xxx.xxx.xxx>;tag=as52b86360

log 2:
From: "203" <sip:203<_at_>xxx.xxx.xxx.xxx>;tag=mfstpfb6wn
To: <sip:sip:201@xxx.xxx.xxx.xxx;user=phone<_at_>xxx.xxx.xxx.xxx;tag=as3813d04b

Best regards,

H.Barlage
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Hi,

it looks like your BLF keys are not configured correctly. There is "sip:sip:".

Filip
  •  
HB

Messages: 32
Karma: 0
Send a private message to this user
BLF is correct !
Lamps are working well !

Same configuration is my local kerio operator !
Only in the cloud everything behind NAT.

Everything else is working well

<sip:201<_at_>xxx.xxx.xxx.xxx;user=phone>|**


Best regards ,

HB

[Updated on: Thu, 28 May 2015 08:37]

  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
I haven't tried BLF behind NAT. It looks like either the phone is misconfigured or broken. I suggest you to contact the snom support or ask in the snom forums.
  •  
M. Steinhauser (Kerio)

Messages: 198

Karma: 7
Send a private message to this user
Hi!
Just reproduced this problem with Snom 360. Other Snom phones with same cfg in same environment works well. But Snom 360 (and probably also yours Snom 320) sends twice "sip:" in header. Try to contact Snom support to solve this problem.

Unfortunately also latest available FW (8.7.3.25) has this error.

Martin

______________________________
Martin Steinhauser
tester
Kerio Technologies
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Good news - we figured it out! The dialplan is causing it. It is a tricky one, because it happens only when there is an outbound route with an empty prefix configured.

We will fix it in Operator 2.4.1. Until then, please modify the provisioning template.

1. Go to Phones->Advanced->Template Overrides
2. Locate Snom 3xx,7xx main configuration file
3. Find line
user_dp_str{$i}$: {$DIALPLAN}

4. Replace it with
user_dp_str{$i}$: !^sip:(.+)$|^(.+)$!sip:\1@\d!

5. Restart the phone

As an alternative you can use the phone web interface and change the Dial-Plan String for each Identity.
  •  
HB

Messages: 32
Karma: 0
Send a private message to this user
Great guys,

tested it and works well !!
tested on snom 300,320,370 and 720
Cool Cool

HB

[Updated on: Thu, 28 May 2015 13:52]

  •  
mjackson

Messages: 64
Karma: 0
Send a private message to this user
Add 821 to the tested list. Problem cleared.
Previous Topic: Message Buttons
Next Topic: Cisco 7937 IP Phone
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: Mon Mar 27 18:31:26 CEST 2017

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