0

Transfer issue

Carlo van Dongen

October 02, 2017 13:41

None

Follow

Hi all,

 

Maybe one of you know a solution.

 

I have a strange problem on a S100 PBX.

When a customer calls to my client, they always got answered by the reception.

The recpetion transfer the call to the end user, but if the end user is not at his/her desk, the reception us a separate intercom to notice the user, this user calls the reception and the reception connect both calls.

 

So far no problem, this works great.

 

Only when the caller is anonymous, the final transfer will fail and the caller ends up in a black hole and will never reach the user.

What do I miss in this case?

• Facebook
• Twitter
• LinkedIn

6 comments

• 0
  
  Carlo van Dongen October 03, 2017 12:47

  In the logs I see a little differance.

  In the log with number I see;

  == Parsing '/etc/asterisk/pjsip.conf': Found
  == Parsing '/etc/asterisk/pjsip_auth.conf': Found
  == Parsing '/etc/asterisk/pjsip_wizard.conf': Found

   

  This is missing in the log without number.

   

• 0
  
  Oscar Colka October 09, 2017 08:48

  What is the firmware version of S100? Is it possible to replicate this issue?

  Did the problem happen every time when the caller is anonymous?

  Is the incoming call from SIP trunk or other kinds of trunk?

• 0
  
  Carlo van Dongen October 10, 2017 06:36

  Hi Oscar,

   

  The firmware version is 30.5.0.8.

  It happens every time with anonymous.

  We use sip trunking and we can reproduce the problem.

  I have log files, only have to make a Pcap.

• 0
  
  Oscar Colka October 11, 2017 05:56

  Carlo,

  I have a same S100 with firmware version 30.5.0.8 but couldn't replicate your problem. I have an incoming call with anonymous caller ID as well.

  What kind of IP phone you are using?

  Did the issue happen after the intercom or it just happen after the transfer?

  Can you post the asterisk CLI logs and the pcap logs?

• 0
  
  Gregory October 11, 2017 06:46

  Hello,

  We also had an issue as described above with an S100
  What we did was take a full backup, cleared the device to factory default and read back the backup.
  The issue never came back.

  I never find the cause of the problem but it still works great for a couple of months now

  Gregory

• 0
  
  Gregory October 17, 2017 08:45

  Hello,

  I guess i was a too quick with my conclusion.

  The issue still exists but they do not transfer this way anymore.

   

  Gregory