FAQ

'Distinctive Ring on Yealink Phones'

A common query for people implementing IP based phone systems is how to have a phone ring differently for internal (from within the office) and external (from the PSTN) calls. To do this you'll need two things; a phones that supports this - here we're using Yealink phones, and a VoIP server that supports the "Alert-info" header - many do such as the popular open source solutions Asterisk and FreeSWITCH. Other than that it's all pretty straight forward.

Firstly we will configure the Yealink phone. To do this go to the "Phone" tab and then to the "Ring" page under that.

Once there add an entry into the first set of boxes. Under "Internal Ringer Text" choose a short descriptive name for the ring, I've called it "Internal" as I'm going to use it to change the ringer for internal calls. Under "Internal Ringer File" select the ring that you would like to use. That's it as far as the Yealink phone configuration goes.

Configuring the VoIP PBX differs depending on the SIP server you are using. For Asterisk you need to set a alertinfo to the extension or incoming rule configuration

'Delayed call setup. dialparties.agi'متن پررنگ'

Delayed call setup. dialparties.agi

Postby ianplain » Tue Aug 16, 2011 3:24 pm Hi

Not realy a question more of a pointer for anyone else having the problem.

We are at the moment setting up an elastix server for a customers call center and all was going well. except for one odd issue. That was a 10 second delay between dialing an extension and it starting to ring.

Code: Select all

   [Aug 16 21:50:04] VERBOSE[9117] pbx.c:     -- Executing [s@macro-dial:3] AGI("SIP/2001-00000000", "dialparties.agi") in new stack
   [Aug 16 21:50:04] VERBOSE[9117] res_agi.c:     -- Launched AGI Script /var/lib/asterisk/agi-bin/dialparties.agi
   [Aug 16 21:50:14] VERBOSE[9117] res_agi.c:  dialparties.agi: Starting New Dialparties.agi

for the logs we see dialparties.agi kicking off then hanging for 10 seconds. CPU load doesn't go up so not a load issue. on investigation and some googling it was found that php its self had an issue.

Code: Select all

   [root@dhcppc2 ~]# time php -v
   PHP 5.1.6 (cli) (built: Mar 31 2010 02:44:37)
   Copyright (c) 1997-2006 The PHP Group
   Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

   real    0m10.02s
   user    0m0.012s
   sys     0m0.003s

heres our delay. :) The server was on the test network and the server had a dns server address in resolv.conf of the default gateway, but that forwards to another gateway and another before getting out, changing resolv.conf to be the actual dns server fixed the issue.

Code: Select all

   [Aug 16 22:01:53] VERBOSE[9158] pbx.c:     -- Executing [s@macro-dial:3] AGI("SIP/2206-00000006", "dialparties.agi") in new stack
   [Aug 16 22:01:53] VERBOSE[9158] res_agi.c:     -- Launched AGI Script /var/lib/asterisk/agi-bin/dialparties.agi
   [Aug 16 22:01:53] VERBOSE[9158] res_agi.c:  dialparties.agi: Starting New Dialparties.agi

Code: Select all

   [root@dhcppc2 ~]# time php -v
   PHP 5.1.6 (cli) (built: Mar 31 2010 02:44:37)
   Copyright (c) 1997-2006 The PHP Group
   Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

   real    0m0.035s
   user    0m0.012s
   sys     0m0.002s