Hello In my ser implementation I have radius accounting for missed calls (busy, not response or offline) and also sems voicemail for those missed calls.
My problem is that if the called-user belongs to the voicemail group and the caller-user cancels the call I see irregular behavior in both ser instances and no Sip-Response-Code=487 is recorded in radius (just an start record without stop) then I see this error in sems debug after 30 seconds:
ERROR: bye (AmRequest.cpp:310): AmRequest::bye: 481 Call Leg/Transaction Does Not Exist please see the ngrep info I send below... some idea?
Also I need to know if its possible to do this: 1. announcement "user_is_offline.wav" if the user exist but it is not connected and it is not in voicemail group. 2. announcement "user_not_exist.wav" if the user is not in the subscriber table. can someone share their configuration file to do this?
Rafael
PS: ngrep -v REGISTER port 5060 below and my configs files in http://rrisco.pub.millicom.com.pe/ser_config_files.txt # U 10.0.0.236:5060 -> 200.110.2.131:5060 INVITE sip:6604000@call.millicom.com.pe SIP/2.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: <sip:66030 ;tag=c500bed0a4..To">00@call.millicom.com.pe>;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@ 10.0.0.236..CSeq: 387 INVITE..Supported: timer..Min-SE: 1800..Date: Thu, 30 Apr 1970 21:29:41 GMT..User-Agent: AddPac SIP Gatew ay..Contact: sip:6603000@10.0.0.236..Content-Type: application/sdp..Content-Length: 182..Max-Forwards: 70....v=0..o=- 10358981 10358981 IN IP4 10.0.0.236..s=AddPac Gateway SDP..c=IN IP4 10.0.0.236..t=0 0..m=audio 23888 RTP/AVP 4 18 0 101..a=rtpmap:101 te lephone-event/8000..a=fmtp:101 0-15.. # U 200.110.2.131:5060 -> 10.0.0.236:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: <sip:66 ;tag=c500bed0a4..To">03000@call.millicom.com.pe>;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055 b2@10.0.0.236..CSeq: 387 INVITE..Server: Sip EXpress router (0.8.99-dev (i386/linux))..Content-Length: 0..Warning: 392 200.110. 2.131:5060 "Noisy feedback tells: pid=1897 req_src_ip=10.0.0.236 req_src_port=5060 in_uri=sip:6604000@call.millicom.com.pe out _uri=sip:6604000@172.18.96.254 via_cnt==1".... # U 200.110.2.131:5060 -> 172.18.96.254:5060 INVITE sip:6604000@172.18.96.254 SIP/2.0..Record-Route: sip:200.110.2.131;ftag=c500bed0a4;lr=on..Via: SIP/2.0/UDP 200.110.2.1 31;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: <sip:6603000@call.millico m.com.pe>;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSe q: 387 INVITE..Supported: timer..Min-SE: 1800..Date: Thu, 30 Apr 1970 21:29:41 GMT..User-Agent: AddPac SIP Gateway..Contact: si p:6603000@10.0.0.236..Content-Type: application/sdp..Content-Length: 182..Max-Forwards: 16....v=0..o=- 10358981 10358981 IN IP4 10.0.0.236..s=AddPac Gateway SDP..c=IN IP4 10.0.0.236..t=0 0..m=audio 23888 RTP/AVP 4 18 0 101..a=rtpmap:101 telephone-event/8 000..a=fmtp:101 0-15.. # U 172.18.96.254:5060 -> 200.110.2.131:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4 bKc500bed0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c510 9e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 INVITE..User-Agent: AddPac SIP Gateway..Content-Length: 0.... # U 172.18.96.254:5060 -> 200.110.2.131:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG 4bKc500bed0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe;tag=4a40522ea 4..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 INVITE..User-Agent: AddPac SIP Gateway..Contact: sip:660 4000@172.18.96.254..Content-Length: 0..Record-Route: sip:200.110.2.131;ftag=c500bed0a4;lr=on.... # U 200.110.2.131:5060 -> 10.0.0.236:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: sip:6603000@call.millicom.com.pe;tag =c500bed0a4..To: sip:6604000@call.millicom.com.pe;tag=4a40522ea4..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..C Seq: 387 INVITE..User-Agent: AddPac SIP Gateway..Contact: sip:6604000@172.18.96.254..Content-Length: 0..Record-Route: <sip:200. 110.2.131;ftag=c500bed0a4;lr=on>.... ######### U 10.0.0.236:5060 -> 200.110.2.131:5060 CANCEL sip:6604000@call.millicom.com.pe SIP/2.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: <sip:66030 ;tag=c500bed0a4..To">00@call.millicom.com.pe>;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@ 10.0.0.236..CSeq: 387 CANCEL..Date: Thu, 30 Apr 1970 21:29:43 GMT..User-Agent: AddPac SIP Gateway..Content-Length: 0..Max-Forwa rds: 70.... # U 200.110.2.131:5060 -> 172.18.96.254:5060 CANCEL sip:6604000@172.18.96.254 SIP/2.0..Record-Route: sip:200.110.2.131;ftag=c500bed0a4;lr=on..Via: SIP/2.0/UDP 200.110.2.1 31;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: <sip:6603000@call.millico m.com.pe>;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSe q: 387 CANCEL..Date: Thu, 30 Apr 1970 21:29:43 GMT..User-Agent: AddPac SIP Gateway..Content-Length: 0..Max-Forwards: 16.... # U 200.110.2.131:5060 -> 10.0.0.236:5060 SIP/2.0 200 cancelling..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed0a4387..From: sip:6603000@call.millicom.com.pe; tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe;tag=a6a1c5f60faecf035a1ae5b6e96e979a-4925..Call-ID: c5109e00-cec1-be2d-8 4d0-0002a40055b2@10.0.0.236..CSeq: 387 CANCEL..Server: Sip EXpress router (0.8.99-dev (i386/linux))..Content-Length: 0..Warning : 392 200.110.2.131:5060 "Noisy feedback tells: pid=1898 req_src_ip=10.0.0.236 req_src_port=5060 in_uri=sip:6604000@call.milli com.com.pe out_uri=sip:6604000@172.18.96.254 via_cnt==1".... ### U 172.18.96.254:5060 -> 200.110.2.131:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc5 00bed0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe..Call-ID: c5109e00 -cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 CANCEL..User-Agent: AddPac SIP Gateway..Content-Length: 0..Record-Route: <si p:200.110.2.131;ftag=c500bed0a4;lr=on>.... ### U 172.18.96.254:5060 -> 200.110.2.131:5060 SIP/2.0 487 Request Terminated..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK2d89.41143714.0..Via: SIP/2.0/UDP 10.0.0.236:5060; branch=z9hG4bKc500bed0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe;ta g=4a40522ea4..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 INVITE..User-Agent: AddPac SIP Gateway..Conte nt-Length: 0.... # U 200.110.2.131:5060 -> 172.18.96.254:5060 ACK sip:6604000@172.18.96.254 SIP/2.0..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK2d89.41143714.0..From: <sip:6603000@call.mi llicom.com.pe>;tag=c500bed0a4..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..To: sip:6604000@call.millicom.com.pe ;tag=4a40522ea4..CSeq: 387 ACK..User-Agent: Sip EXpress router(0.8.99-dev (i386/linux))..Content-Length: 0.... # U 200.110.2.131:5060 -> 10.0.0.236:5060 SIP/2.0 180 ringing..Record-Route: sip:200.110.2.131;ftag=c500bed0a4;lr=on..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc5 00bed0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe;tag=0000356755B227 CF..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 INVITE..Contact: sip:6604000@200.110.2.131:5090..Serv er: Sip EXpress router (0.8.99-dev (i386/linux))..Content-Length: 0..Warning: 392 200.110.2.131:5090 "Noisy feedback tells: pi d=1933 req_src_ip=200.110.2.131 req_src_port=5060 in_uri=sip:6604000@call.millicom.com.pe:5090 out_uri=sip:6604000@call.millico m.com.pe:5090 via_cnt==0".... # . . . . # U 200.110.2.131:5060 -> 10.0.0.236:5060 SIP/2.0 200 OK..Record-Route: sip:200.110.2.131;ftag=c500bed0a4;lr=on..Via: SIP/2.0/UDP 10.0.0.236:5060;branch=z9hG4bKc500bed 0a4387..From: sip:6603000@call.millicom.com.pe;tag=c500bed0a4..To: sip:6604000@call.millicom.com.pe;tag=0000356755B227CF..C all-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 387 INVITE..Contact: sip:6604000@200.110.2.131:5090..Content-T ype: application/sdp..Server: Sip EXpress router (0.8.99-dev (i386/linux))..Content-Length: 123..Warning: 392 200.110.2.131:509 0 "Noisy feedback tells: pid=1933 req_src_ip=200.110.2.131 req_src_port=5060 in_uri=sip:6604000@call.millicom.com.pe:5090 out_ uri=sip:6604000@call.millicom.com.pe:5090 via_cnt==0"....v=0..o=username 0 0 IN IP4 200.110.2.131..s=session..c=IN IP4 200.110. 2.131..t=0 0..m=audio 1418 RTP/AVP 0..a=rtpmap:0 /... # U 200.110.2.131:5060 -> 10.0.0.236:5060 BYE sip:6603000@10.0.0.236 SIP/2.0..Max-Forwards: 10..Record-Route: sip:200.110.2.131;ftag=0000356755B227CF;lr=on..Via: SIP/2 .0/UDP 200.110.2.131;branch=z9hG4bK0e89.94661d82.0..Via: SIP/2.0/UDP 200.110.2.131:5090;branch=z9hG4bK0e89.ce855942.0..To: <sip :6603000@call.millicom.com.pe>;tag=c500bed0a4..From: sip:6604000@call.millicom.com.pe;tag=0000356755B227CF..CSeq: 388 BYE..Ca ll-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..Content-Length: 0..User-Agent: Sip EXpress router(0.8.99-dev (i386/linu x))..Contact: sip:6604000@200.110.2.131:5090..P-MsgFlags: 0..Min-SE: 1800..Date: Thu, 30 Apr 1970 21:29:41 GMT.... # U 10.0.0.236:5060 -> 200.110.2.131:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 200.110.2.131;branch=z9hG4bK0e89.94661d82.0..Via: SIP/2.0/UDP 200.110.2.131:5090;branch=z9hG4bK0e89.ce855942.0..From: sip:6604000@call.millicom.com.pe;tag=0000356755B227CF..To: <sip:6603 ;tag=c500bed0a4..Call-ID">000@call.millicom.com.pe>;tag=c500bed0a4..Call-ID: c5109e00-cec1-be2d-84d0-0002a40055b2@10.0.0.236..CSeq: 388 BYE..User-Agent: AddPac SIP Gateway..Content-Length: 0....
#########################
--------------------------------- Do You Yahoo!? Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo. Visíta Yahoo! Noticias.