[Serusers] ACC into mysql

[Barry Murphy]

MessageThanks,

After months of trying to get this working, your solution fixed the problem. Now the only issue I have is the following:

When I call 03 ( UA -> SER -> Asterisk ) the date and time is read out to the user, asterisk then hangs up the call, however SER doesn't see the hangup, I have to manualy click hangup and then SER gives the BYE.

Apr 27 12:09:04 max /usr/local/sbin/ser[30538]: ACC: transaction answered: call_id=93EF8C43-C9E2-4E4C-997C-B1A4DA8FD137 at 10.200.3.173, totag=as113261f7, from=6494485566 <sip:6494485566 at voip.fast.co.nz>;tag=3875371437, i-uri=sip:03 at voip.fast.co.nz, method=INVITE, o-uri=sip:03 at 202.150.105.150:5070, fromtag=3875371437, code=200, to=<sip:03 at voip.fast.co.nz>;tag=as113261f7, uid=n/a, userpart=03
Apr 27 12:09:04 max /usr/local/sbin/ser[30541]: ACC: request acknowledged: call_id=93EF8C43-C9E2-4E4C-997C-B1A4DA8FD137 at 10.200.3.173, totag=as113261f7, from=6494485566 <sip:6494485566 at voip.fast.co.nz>;tag=3875371437, i-uri=sip:03 at 202.150.105.150:5070, method=ACK, o-uri=sip:03 at 202.150.105.150:5070, fromtag=3875371437, code=200, to=<sip:03 at voip.fast.co.nz>;tag=as113261f7, uid=n/a, userpart=03
Apr 27 12:09:33 max /usr/local/sbin/ser[30537]: ACC: transaction answered: call_id=93EF8C43-C9E2-4E4C-997C-B1A4DA8FD137 at 10.200.3.173, totag=as113261f7, from=6494485566 <sip:6494485566 at voip.fast.co.nz>;tag=3875371437, i-uri=sip:03 at 202.150.105.150:5070, method=BYE, o-uri=sip:03 at 202.150.105.150:5070, fromtag=3875371437, code=200, to=<sip:03 at voip.fast.co.nz>;tag=as113261f7, uid=n/a, userpart=03

Any ideas?

Thanks
Barry


  ----- Original Message ----- 
  From: Matt Schulte 
  To: Edgardo O. Gonzales II ; Kofi Obiri-Yeboah 
  Cc: serusers at lists.iptel.org 
  Sent: Wednesday, April 27, 2005 1:13 AM
  Subject: RE: [Serusers] ACC into mysql


  This particular config (I don't think?) won't log to a DB, additionally you need to setflag(1); somewhere in your config. We tried to set on "outbound" only originally and didn't have much luck so I set it near the top. To log to (my)sql you will additionally need to set another flag and setup similar mod params:


  modparam("acc", "db_url", "mysql://ser:serro@blah.mysql.haha/dbname")
  # Note flag 2, you will need to setflag(1); AND setflag(2);
  modparam("acc", "db_flag", 2)

  #Note this one logs all failed calls from the invite response, I find it useful
  modparam("acc", "failed_transactions", 1)

  # In your route config use something like the following

  # This is pretty much near the top, while ACC won't log reg's or INFO anyway, I just thought it'd be a little cleaner to have
  ...
  if (!method == "REGISTER" || !method == "INFO" ) {
                  setflag(1);
                  setflag(2);
  }
  ...

  # Doing the above ensure everything gets tagged including BYE's. A good reason why your BYE's may not get
  # tagged is possibly because record-route could be relaying the call before the flag gets set, just a thought..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050427/cf932e40/attachment.htm>