[Serusers] SER + asterisk

Patrick Baker patricksbaker at gmail.com
Mon Jan 31 08:46:54 CET 2005


Hello,

I'm trying to get asterisk to work with SER - I have ser forwarding
the sip connection to asterisk with the following routing logic.

        if (uri=~"^sip:8[0-9]{7}.*") {
                forward( 10.0.18.3, 5061 );
                break;

Asterisk accepts the connection on port 5061 - but I get the following
once it connects to asterisk.

001    -- Executing Answer("SIP/ast.digicen.com-08289858", "") in new stack
002     -- Executing Dial("SIP/ast.digicen.com-08289858",
"IAX2/kknott at NuFone/12039063173") in new stack
003     -- Called kknott at NuFone/12039063173
004     -- Call accepted by 66.225.202.72 (format gsm)
005     -- Format for call is gsm
006     -- Hungup 'IAX2/NuFone/1'
007   == No one is available to answer at this time (1:0/0/0)
008   == Auto fallthrough, channel 'SIP/ast.digicen.com-08289858'
status is 'NOANSWER'
009        > cdr_odbc: Query Successful!
010 Jan 30 21:41:42 WARNING[9829]: chan_sip.c:2551 parse: Too many SIP
headers...
011 Jan 30 21:41:42 WARNING[9829]: chan_sip.c:2551 parse: Too many SIP
headers...
012 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2551 parse: Too many SIP
headers...
013 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2551 parse: Too many SIP
headers...
014 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2551 parse: Too many SIP
headers...
015 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
016 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
017 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
018 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
019 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
020 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
021 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
022 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
023 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
024 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
025 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
026 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
027 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
028 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
029 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
030 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
031 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
032 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
033 Jan 30 21:41:43 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
034 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
035 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
036 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
037 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
038 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
039 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
040 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
041 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
042 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
043 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
044 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
045 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
046 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
047 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
048 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
049 Jan 30 21:41:44 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
050 Jan 30 21:41:45 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
051 Jan 30 21:41:45 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
052 Jan 30 21:41:45 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
053 Jan 30 21:41:45 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
054 Jan 30 21:41:45 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
055 Jan 30 21:41:46 WARNING[9829]: chan_sip.c:729 retrans_pkt: Maximum
retries exceeded on call
5A2650C2-94B0-44AB-B241-66DB67BE2CF7 at 192.168.1.104 for seqno 52428
(Non-critical Response)
056 Jan 30 21:41:46 WARNING[9829]: chan_sip.c:729 retrans_pkt: Maximum
retries exceeded on call
5A2650C2-94B0-44AB-B241-66DB67BE2CF7 at 192.168.1.104 for seqno 102
(Non-critical Request)
057 Jan 30 21:41:50 WARNING[9829]: chan_sip.c:2385 find_call: Call
missing call ID from '24.181.176.62'
058 
059 *CLI>
060 *CLI>

Asterisk will usually core dump after that - I have no idea where to
start to fix it - No machines are behind NAT.

Thanks,


Patrick




More information about the sr-users mailing list