Help - Dropped calls when entering meetme conference

[ianwild]

Hi Guys,

Does anyone have any idea about possible cause of this? My users randomly have to redial to successfully connect to their conferences. The DID is a number from DIDforsale, set-up as per the instructions here. This happens intermittently before users actually get connected to the meetme conference - They just hear silence but they don't actually get hung-up on. I've got 5 examples of similar things from today. Here's just two:

EG One

[2009-07-07 18:01:46] VERBOSE[11560] logger.c: -- <SIP/5060-08e5efe0> Playing 'vm-rec-name' (language 'en')
[2009-07-07 18:01:48] WARNING[3829] chan_sip.c: Maximum retries exceeded on transmission a0f3b6305056adc713c4716cf1bb11aaee1648071c0e2910-0203-7921 for seqno 1 (Critical Response)
[2009-07-07 18:01:48] WARNING[3829] chan_sip.c: Hanging up call a0f3b6305056adc713c4716cf1bb11aaee1648071c0e2910-0203-7921 - no reply to our critical packet.
[2009-07-07 18:01:48] VERBOSE[11560] logger.c: == Spawn extension (ext-meetme, STARTMEETME, 1) exited non-zero on 'SIP/5060-08e5efe0'
[2009-07-07 18:01:48] VERBOSE[11560] logger.c: -- Executing [h@ext-meetme:1] Hangup("SIP/5060-08e5efe0", "") in new stack

Two:

[2009-07-07 18:05:11] VERBOSE[11597] logger.c: -- <SIP/5060-08e3f988> Playing 'conf-otherinparty' (language 'en')
[2009-07-07 18:05:13] WARNING[3829] chan_sip.c: Maximum retries exceeded on transmission a0f47b485056adc713c47179c1bb43c30a24fdbf4c07edc0-0204-7742 for seqno 1 (Critical Response)
[2009-07-07 18:05:13] WARNING[3829] chan_sip.c: Hanging up call a0f47b485056adc713c47179c1bb43c30a24fdbf4c07edc0-0204-7742 - no reply to our critical packet.
[2009-07-07 18:05:13] VERBOSE[11597] logger.c: == Spawn extension (ext-meetme, STARTMEETME, 1) exited non-zero on 'SIP/5060-08e3f988'
[2009-07-07 18:05:13] VERBOSE[11597] logger.c: -- Executing [h@ext-meetme:1] Hangup("SIP/5060-08e3f988", "") in new stack
[2009-07-07 18:05:13] VERBOSE[11597] logger.c: == Spawn extension (ext-meetme, h, 1) exited non-zero on 'SIP/5060-08e3f988'

I'm running PIAF with the Orgasmatron Installer on a HP-Proliant ML115 G5 with 2GB of RAM.

Some details:
* Running Asterisk Version : Asterisk 1.4.21.2
* Asterisk Source Version : 1.4.21.2
* Zaptel Source Version : 1.4.12.1
* Libpri Source Version : 1.4.7
* Addons Source Version : 1.4.7
********************************************************************
shef-pbx on 10.1.13.10 - eth0
CentOS release 5.3 (Final) :32 Bit Kernel: 2.6.18-128.1.14.el5

Any ideas folks?

Ian

 

[ianwild]

Lots more of the same today - I wish I knew where to start troubleshootig this one. None of the stuff in Google seems relevant.

[2009-07-08 18:11:43] VERBOSE[30467] logger.c: -- Created MeetMe conference 1022 for conference '821'
[2009-07-08 18:11:43] VERBOSE[30467] logger.c: -- <SIP/5060-09c8fd90> Playing 'vm-rec-name' (language 'en')
[2009-07-08 18:11:44] WARNING[16618] chan_sip.c: Maximum retries exceeded on transmission a01481905056adc713c486a9d20e0783ee0115707bf4ef80-0204-5337 for seqno 1 (Critical Response)
[2009-07-08 18:11:44] WARNING[16618] chan_sip.c: Hanging up call a01481905056adc713c486a9d20e0783ee0115707bf4ef80-0204-5337 - no reply to our critical packet.
[2009-07-08 18:11:44] VERBOSE[30467] logger.c: -- Hungup 'Zap/pseudo-840022601'
[2009-07-08 18:11:44] VERBOSE[30467] logger.c: == Spawn extension (ext-meetme, STARTMEETME, 1) exited non-zero on 'SIP/5060-09c8fd90'
[2009-07-08 18:11:44] VERBOSE[30467] logger.c: -- Executing [h@ext-meetme:1] Hangup("SIP/5060-09c8fd90", "") in new stack
[2009-07-08 18:11:44] VERBOSE[30467] logger.c: == Spawn extension (ext-meetme, h, 1) exited non-zero on 'SIP/5060-09c8fd90'
[2009-07-08 18:11:45] WARNING[16618] chan_sip.c: Maximum retries exceeded on transmission a248a0a05056adc713c486a9e20e07bde7aad4ba0c0cce58-0203-6253 for seqno 1 (Critical Response)
[2009-07-08 18:11:45] WARNING[16618] chan_sip.c: Hanging up call a248a0a05056adc713c486a9e20e07bde7aad4ba0c0cce58-0203-6253 - no reply to our critical packet.
[2009-07-08 18:11:45] WARNING[30468] file.c: Failed to write frame
[2009-07-08 18:11:45] VERBOSE[30468] logger.c: -- <SIP/5060-09c5b0f8> Playing 'vm-goodbye' (language 'en')

If no one else is seeing this is it worth me re-installing? It's a pain but I can't leave it as it is.

 

[ianwild]

The good news is that this is teaching me loads - Shouldn't jump to conclusions. In fact Google has this well covered. I just need to figure out what to change to fix it.

Meetme is a red herring. Here's some Log samples.


Fail 1:

[2009-07-08 18:04:24] VERBOSE[29853] logger.c: -- Executing [1925808xxxx@from-pstn:1] Set("SIP/5060-b7800478",
[2009-07-08 18:04:43] VERBOSE[29853] logger.c: -- <SIP/5060-b7800478> Playing 'vm-rec-name' (language 'en')
[2009-07-08 18:04:44] WARNING[16618] chan_sip.c: Maximum retries exceeded on transmission

Fail 2:

[2009-07-08 18:12:19] VERBOSE[30488] logger.c: -- Executing [1925808xxxx@from-pstn:1] Set("SIP/5060-09c9e660",
[2009-07-08 18:12:37] VERBOSE[30488] logger.c: -- <SIP/5060-09c9e660> Playing 'vm-rec-name' (language 'en')
[2009-07-08 18:12:39] WARNING[16618] chan_sip.c: Maximum retries exceeded on transmission a0099ac85056adc713c486ad420e14f21907acfeec168978-0203-6255 for seqno 1 (Critical Response)

Fail 3:

[2009-07-08 18:11:24] VERBOSE[30467] logger.c: -- Executing [1925808xxxx@from-pstn:1] Set("SIP/5060-09c8fd90",
[2009-07-08 18:11:43] VERBOSE[30467] logger.c: -- <SIP/5060-09c8fd90> Playing 'vm-rec-name' (language 'en')
[2009-07-08 18:11:44] WARNING[16618] chan_sip.c: Maximum retries exceeded on transmission a01481905056adc713c486a9d20e0783ee0115707bf4ef80-0204-5337 for seqno 1 (Critical Response)

Back to Google to find the best solution to the call being dropped exactly 20 seconds after it's connected.

Ian