Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 28/05/2004
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 28/05/2004
Thanks a lot,
I'm now using lates ser stable CVS+mediaproxy.
But in the register process i got this error (the user get successfully register), please advise if this is a normal messsage.
.... /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body ....
Ri Liang ------------------------------------------------------------------------------------------------------ /ser[8813]: method: <REGISTER> /ser[8813]: uri: sip:192.168.2.3 /ser[8813]: version: <SIP/2.0> /ser[8813]: parse_headers: flags=1 /ser[8813]: Found param type 232, <branch> = <z9hG4bK3e28f0599ccb9b4a>; state=16 /ser[8813]: end of header reached, state=5 /ser[8813]: parse_headers: Via found, flags=1 /ser[8813]: parse_headers: this is the first via /ser[8813]: After parse_msg... /ser[8813]: preparing to run routing scripts... /ser[8813]: DEBUG : is_maxfwd_present: searching for max_forwards header /ser[8813]: parse_headers: flags=128 /ser[8813]: end of header reached, state=9 /ser[8813]: DEBUG: get_hdr_field: <To> [35]; uri=[sip:2222@192.168.2.3;user=phone] /ser[8813]: DEBUG: to body [sip:2222@192.168.2.3;user=phone^M ] /ser[8813]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> /ser[8813]: DEBUG: is_maxfwd_present: value = 70 /ser[8813]: parse_headers: flags=64 /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: parse_headers: flags=256 /ser[8813]: DEBUG: get_hdr_body : content_length=0 /ser[8813]: found end of header /ser[8813]: find_first_route(): No Route headers found /ser[8813]: loose_route(): There is no Route HF /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: parse_headers: flags=4096 /ser[8813]: pre_auth(): Credentials with given realm not found /ser[8813]: build_auth_hf(): 'WWW-Authenticate: Digest realm="sip.callmyway.net", nonce="40bec3e4d09adf671de759a294bcdca543de6efc"^M ' /ser[8813]: parse_headers: flags=-1 /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: receive_msg: cleaning up /ser[8811]: SIP Request:
------------------------------------------------------------------------------------------------------ ----- Original Message ----- From: Tjapko ITS Consult@ncy To: Adrian Georgescu ; rliang@callmyway.com Cc: serusers@lists.iptel.org Sent: Tuesday, June 01, 2004 5:24 AM Subject: RE: [Serusers] ser stable + mediaproxy
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
You should apply the functions from the module to INVITE and REGISTER only. Messages having no contact header will give the warning which is harmless but your config needs some tuning.
Adrian
On Jun 3, 2004, at 9:23 AM, Ri Liang wrote:
Thanks a lot, I'm now using lates ser stable CVS+mediaproxy. But in the register process i got this error (the user get successfully register), please advise if this is a normal messsage. .... /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body .... Ri Liang
/ser[8813]: method: <REGISTER> /ser[8813]: uri: sip:192.168.2.3 /ser[8813]: version: <SIP/2.0> /ser[8813]: parse_headers: flags=1 /ser[8813]: Found param type 232, <branch> = <z9hG4bK3e28f0599ccb9b4a>; state=16 /ser[8813]: end of header reached, state=5 /ser[8813]: parse_headers: Via found, flags=1 /ser[8813]: parse_headers: this is the first via /ser[8813]: After parse_msg... /ser[8813]: preparing to run routing scripts... /ser[8813]: DEBUG : is_maxfwd_present: searching for max_forwards header /ser[8813]: parse_headers: flags=128 /ser[8813]: end of header reached, state=9 /ser[8813]: DEBUG: get_hdr_field: <To> [35]; uri=[sip:2222@192.168.2.3;user=phone] /ser[8813]: DEBUG: to body [sip:2222@192.168.2.3;user=phone^M ] /ser[8813]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> /ser[8813]: DEBUG: is_maxfwd_present: value = 70 /ser[8813]: parse_headers: flags=64 /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: parse_headers: flags=256 /ser[8813]: DEBUG: get_hdr_body : content_length=0 /ser[8813]: found end of header /ser[8813]: find_first_route(): No Route headers found /ser[8813]: loose_route(): There is no Route HF /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: parse_headers: flags=4096 /ser[8813]: pre_auth(): Credentials with given realm not found /ser[8813]: build_auth_hf(): 'WWW-Authenticate: Digest realm="sip.callmyway.net", nonce="40bec3e4d09adf671de759a294bcdca543de6efc"^M ' /ser[8813]: parse_headers: flags=-1 /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: receive_msg: cleaning up /ser[8811]: SIP Request:
----- Original Message ----- From: Tjapko ITS Consult@ncy To: Adrian Georgescu ; rliang@callmyway.com Cc: serusers@lists.iptel.org Sent: Tuesday, June 01, 2004 5:24 AM Subject: RE: [Serusers] ser stable + mediaproxy
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
Hello,
I got the said error on a REGISTER.
And i'm using the standar nathelper.cfg (modified with mediaproxy commands).
Regards,
Ri Liang ----- Original Message ----- From: Adrian Georgescu To: Ri Liang Cc: tjapko@xeloq.com ; serusers@lists.iptel.org Sent: Thursday, June 03, 2004 1:52 AM Subject: Re: [Serusers] ser stable + mediaproxy
You should apply the functions from the module to INVITE and REGISTER only. Messages having no contact header will give the warning which is harmless but your config needs some tuning.
Adrian
On Jun 3, 2004, at 9:23 AM, Ri Liang wrote:
Thanks a lot,
I'm now using lates ser stable CVS+mediaproxy.
But in the register process i got this error (the user get successfully register), please advise if this is a normal messsage.
.... /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body ....
Ri Liang ------------------------------------------------------------------------------------------------------ /ser[8813]: method: <REGISTER> /ser[8813]: uri: sip:192.168.2.3 /ser[8813]: version: <SIP/2.0> /ser[8813]: parse_headers: flags=1 /ser[8813]: Found param type 232, <branch> = <z9hG4bK3e28f0599ccb9b4a>; state=16 /ser[8813]: end of header reached, state=5 /ser[8813]: parse_headers: Via found, flags=1 /ser[8813]: parse_headers: this is the first via /ser[8813]: After parse_msg... /ser[8813]: preparing to run routing scripts... /ser[8813]: DEBUG : is_maxfwd_present: searching for max_forwards header /ser[8813]: parse_headers: flags=128 /ser[8813]: end of header reached, state=9 /ser[8813]: DEBUG: get_hdr_field: <To> [35]; uri=[sip:2222@192.168.2.3;user=phone] /ser[8813]: DEBUG: to body [sip:2222@192.168.2.3;user=phone^M ] /ser[8813]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> /ser[8813]: DEBUG: is_maxfwd_present: value = 70 /ser[8813]: parse_headers: flags=64 /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: parse_headers: flags=256 /ser[8813]: DEBUG: get_hdr_body : content_length=0 /ser[8813]: found end of header /ser[8813]: find_first_route(): No Route headers found /ser[8813]: loose_route(): There is no Route HF /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: parse_headers: flags=4096 /ser[8813]: pre_auth(): Credentials with given realm not found /ser[8813]: build_auth_hf(): 'WWW-Authenticate: Digest realm="sip.callmyway.net", nonce="40bec3e4d09adf671de759a294bcdca543de6efc"^M ' /ser[8813]: parse_headers: flags=-1 /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: receive_msg: cleaning up /ser[8811]: SIP Request:
------------------------------------------------------------------------------------------------------ ----- Original Message ----- From: Tjapko ITS Consult@ncy To: Adrian Georgescu ; rliang@callmyway.com Cc: serusers@lists.iptel.org Sent: Tuesday, June 01, 2004 5:24 AM Subject: RE: [Serusers] ser stable + mediaproxy
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
Hello,
Mediaproxy is working fine when there is only one session.
When a second session jumps in, the audio gets very bad (you can no understand at all).
When some of the session ends, the audio gets back OK for the remaining session.
Please adivse how i can solve this problem.
I am using the standar ser.cfg that comes for nathelper modified to use mediaproxy.
Thanks in advance,
Ri Liang
----- Original Message ----- From: Adrian Georgescu To: Ri Liang Cc: tjapko@xeloq.com ; serusers@lists.iptel.org Sent: Thursday, June 03, 2004 1:52 AM Subject: Re: [Serusers] ser stable + mediaproxy
You should apply the functions from the module to INVITE and REGISTER only. Messages having no contact header will give the warning which is harmless but your config needs some tuning.
Adrian
On Jun 3, 2004, at 9:23 AM, Ri Liang wrote:
Thanks a lot,
I'm now using lates ser stable CVS+mediaproxy.
But in the register process i got this error (the user get successfully register), please advise if this is a normal messsage.
.... /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body ....
Ri Liang ------------------------------------------------------------------------------------------------------ /ser[8813]: method: <REGISTER> /ser[8813]: uri: sip:192.168.2.3 /ser[8813]: version: <SIP/2.0> /ser[8813]: parse_headers: flags=1 /ser[8813]: Found param type 232, <branch> = <z9hG4bK3e28f0599ccb9b4a>; state=16 /ser[8813]: end of header reached, state=5 /ser[8813]: parse_headers: Via found, flags=1 /ser[8813]: parse_headers: this is the first via /ser[8813]: After parse_msg... /ser[8813]: preparing to run routing scripts... /ser[8813]: DEBUG : is_maxfwd_present: searching for max_forwards header /ser[8813]: parse_headers: flags=128 /ser[8813]: end of header reached, state=9 /ser[8813]: DEBUG: get_hdr_field: <To> [35]; uri=[sip:2222@192.168.2.3;user=phone] /ser[8813]: DEBUG: to body [sip:2222@192.168.2.3;user=phone^M ] /ser[8813]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> /ser[8813]: DEBUG: is_maxfwd_present: value = 70 /ser[8813]: parse_headers: flags=64 /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: parse_headers: flags=256 /ser[8813]: DEBUG: get_hdr_body : content_length=0 /ser[8813]: found end of header /ser[8813]: find_first_route(): No Route headers found /ser[8813]: loose_route(): There is no Route HF /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: parse_headers: flags=4096 /ser[8813]: pre_auth(): Credentials with given realm not found /ser[8813]: build_auth_hf(): 'WWW-Authenticate: Digest realm="sip.callmyway.net", nonce="40bec3e4d09adf671de759a294bcdca543de6efc"^M ' /ser[8813]: parse_headers: flags=-1 /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: receive_msg: cleaning up /ser[8811]: SIP Request:
------------------------------------------------------------------------------------------------------ ----- Original Message ----- From: Tjapko ITS Consult@ncy To: Adrian Georgescu ; rliang@callmyway.com Cc: serusers@lists.iptel.org Sent: Tuesday, June 01, 2004 5:24 AM Subject: RE: [Serusers] ser stable + mediaproxy
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
Difficult. Normally not the download but the upload (in your case only 64) is causing the problems if there is not enough bandwith available. Sessions.py only shows you the consumption for the calls. Are you sure you aren't using more bandwith with other applications. Furthermore you should check the jitter buffer size in your EP's and be sure that you locally do not have lan congestion problems caused by bad components in your chain. If you use g729 than this also means that your processor is being charged. Use a monitor tool to see your processor load also use a monitor tool to check the total bandwith consumption on your server and check again. I have tested in the same configuration with > 5 Ep's on my development server and g729 without problems. Tjapko.
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Ri Liang Sent: Domingo, 06 de Junio de 2004 10:10 a.m. To: Adrian Georgescu Cc: tjapko@xeloq.com; serusers@lists.iptel.org Subject: Re: [Serusers] ser stable + mediaproxy
Hello,
Mediaproxy is working fine when there is only one session.
When a second session jumps in, the audio gets very bad (you can no understand at all).
When some of the session ends, the audio gets back OK for the remaining session.
Please adivse how i can solve this problem.
I am using the standar ser.cfg that comes for nathelper modified to use mediaproxy.
Thanks in advance,
Ri Liang
----- Original Message ----- From: Adrian Georgescu To: Ri Liang Cc: tjapko@xeloq.com ; serusers@lists.iptel.org Sent: Thursday, June 03, 2004 1:52 AM Subject: Re: [Serusers] ser stable + mediaproxy
You should apply the functions from the module to INVITE and REGISTER only. Messages having no contact header will give the warning which is harmless but your config needs some tuning.
Adrian
On Jun 3, 2004, at 9:23 AM, Ri Liang wrote:
Thanks a lot,
I'm now using lates ser stable CVS+mediaproxy.
But in the register process i got this error (the user get successfully register), please advise if this is a normal messsage.
.... /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body ....
Ri Liang ---------------------------------------------------------------------- -------------------------------- /ser[8813]: method: <REGISTER> /ser[8813]: uri: sip:192.168.2.3 /ser[8813]: version: <SIP/2.0> /ser[8813]: parse_headers: flags=1 /ser[8813]: Found param type 232, <branch> = <z9hG4bK3e28f0599ccb9b4a>; state=16 /ser[8813]: end of header reached, state=5 /ser[8813]: parse_headers: Via found, flags=1 /ser[8813]: parse_headers: this is the first via /ser[8813]: After parse_msg... /ser[8813]: preparing to run routing scripts... /ser[8813]: DEBUG : is_maxfwd_present: searching for max_forwards header /ser[8813]: parse_headers: flags=128 /ser[8813]: end of header reached, state=9 /ser[8813]: DEBUG: get_hdr_field: <To> [35]; uri=[sip:2222@192.168.2.3;user=phone] /ser[8813]: DEBUG: to body [sip:2222@192.168.2.3;user=phone^M ] /ser[8813]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> /ser[8813]: DEBUG: is_maxfwd_present: value = 70 /ser[8813]: parse_headers: flags=64 /ser[8813]: error: mediaproxy/getContactURI(): error parsing Contact body /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: parse_headers: flags=256 /ser[8813]: DEBUG: get_hdr_body : content_length=0 /ser[8813]: found end of header /ser[8813]: find_first_route(): No Route headers found /ser[8813]: loose_route(): There is no Route HF /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==9 && [192.168.2.3] == [127.0.0.1] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: check_self - checking if host==us: 11==11 && [192.168.2.3] == [192.168.2.3] /ser[8813]: check_self - checking if port 5060 matches port 5060 /ser[8813]: parse_headers: flags=4096 /ser[8813]: pre_auth(): Credentials with given realm not found /ser[8813]: build_auth_hf(): 'WWW-Authenticate: Digest realm="sip.callmyway.net", nonce="40bec3e4d09adf671de759a294bcdca543de6efc"^M ' /ser[8813]: parse_headers: flags=-1 /ser[8813]: check_via_address(192.168.2.22, 192.168.2.22, 0) /ser[8813]: receive_msg: cleaning up /ser[8811]: SIP Request:
---------------------------------------------------------------------- -------------------------------- ----- Original Message ----- From: Tjapko ITS Consult@ncy To: Adrian Georgescu ; rliang@callmyway.com Cc: serusers@lists.iptel.org Sent: Tuesday, June 01, 2004 5:24 AM Subject: RE: [Serusers] ser stable + mediaproxy
Hello, I had same problem. Use stable 0.8.12 SER from latest CVS and mediaproxy from latest CVS head. Recompile this and it should work. Do not use rpm or tarball to create your SER. Hope this helps. I have discovered more things that are causing problems implementing SER with Mediaproxy. Tjapko. -----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Adrian Georgescu Sent: Martes, 01 de Junio de 2004 03:38 a.m. To: rliang@callmyway.com Cc: serusers@lists.iptel.org Subject: [Serusers] ser stable + mediaproxy
Hi Ri,
We use successfully mediaproxy with both stable and unstable branches of ser on Debian systems. There is no known reason it should crash, maybe IPTEL guys would have more clues as I saw this problem being reported several time.
Adrian
-- Hello,
I'm using lates ser CVS stable with mediaproxy (from unstable ser directory and also using the mysql create with unstable ser_mysql.sh).
SER crash in the same moment when a sip cliente get register with the correct user and password, i have attach the syslog.
Am I using the right combination of SER+mediaproxy ? or do i need to use only the unstable ser (with it's mediaproxy include).
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.699 / Virus Database: 456 - Release Date: 04/06/2004
-
Adrian Georgescu -
Ri Liang -
Tjapko ITS Consult＠ncy