Hi,
I tried to use SIP register method to upload cpl script. However I got a result "bad request". The algorithm used in cpled is set as null. I thought normally that it should be md5. The ser's debug message says "Credentials received are not filled properly".
Can someone help me please?
Thanks, Richard
P.S. Has anyone used cpl extensively? Is it reasonably stable?
__________________________________ Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. http://promo.yahoo.com/sbc/
REGISTER sip:example.org SIP/2.0. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 1 REGISTER. Contact: sip:41.222.132.128:8700. Content-Type: application/cpl+xml. Content-Disposition: script;action=store. Content-Length: 1044. . <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
<cpl> <subaction id="trash" /> <subaction id="voicemail"> <location url="sip:55592@example.org" priority="0.0" clear="yes"> <redirect /> </location> </subaction> <incoming> <address-switch field="destination" subfield="user"> <address is="user@host"> <location url="sip:55592@example.org"> <proxy> <busy> <time-switch tzid="HST -10"> <time dtstart="20040510T151502" duration="P28DT00H00M00S" freq="weekly" interval="001" byday="MO,WE,FR" bymonthday="1-5,8-10" byyearday="10-20" bymonth="1,4,7,10" /> </time-switch> </busy> <noanswer> <sub ref="voicemail" /> </noanswer> <failure> <lookup source="gost.com" /> </failure> </proxy> </location> </address> <otherwise /> </address-switch> </incoming> </cpl>
# U +0.003535 41.222.132.128:5060 -> 41.222.132.128:8700 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 1 REGISTER. WWW-Authenticate: Digest realm="example.org", nonce="40a48d4ba435a6dff240e5ceabc9fc5296089728", qop="auth". Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
# U +0.002629 41.222.132.128:33739 -> 41.222.132.128:5060 REGISTER sip:example.org SIP/2.0. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Authorization: Digest username="888", realm="example.org", uri="sip:example.org", algorithm=null, nonce="40a48d4ba435a6dff240e5ceabc9fc5296089728", qop="auth", cnonce="fc82c359317018651a99347", response="f0ad5bb30d3d1f11fc31bb69bd54bbab". Contact: sip:41.222.132.128:8700. Content-Type: application/cpl+xml. Content-Disposition: script;action=store. Content-Length: 1044. . <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
<cpl> <subaction id="trash" /> <subaction id="voicemail"> <location url="sip:55592@example.org" priority="0.0" clear="yes"> <redirect /> </location> </subaction> <incoming> <address-switch field="destination" subfield="user"> <address is="user@host"> <location url="sip:55592@example.org"> <proxy> <busy> <time-switch tzid="HST -10"> <time dtstart="20040510T151502" duration="P28DT00H00M00S" freq="weekly" interval="001" byday="MO,WE,FR" bymonthday="1-5,8-10" byyearday="10-20" bymonth="1,4,7,10" /> </time-switch> </busy> <noanswer> <sub ref="voicemail" /> </noanswer> <failure> <lookup source="gost.com" /> </failure> </proxy> </location> </address> <otherwise /> </address-switch> </incoming> </cpl>
# U +0.002369 41.222.132.128:5060 -> 41.222.132.128:8700 SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
# U +0.001366 41.222.132.128:5060 -> 41.222.132.128:8700 SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
# I +0.000035 41.222.132.128 -> 41.222.132.128 3:3 ....E.....@.@...B...B.....!...#.SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
## U +0.002265 41.222.132.128:5060 -> 41.222.132.128:8700 SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
# I +0.000024 41.222.132.128 -> 41.222.132.128 3:3 ....E.....@.@...B...B.....!...#.SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP 41.222.132.128:8700. From: sip:888@example.org. To: sip:888@example.org;tag=b756ea191e1a1705f44b2100b0983a34.0f1f. Call-ID: 14tg4341-1084525599016-295028-32961147@41.222.132.128. CSeq: 2 REGISTER. Server: Sip EXpress router (0.8.13-dev-28 (i386/linux)). Content-Length: 0. Warning: 392 41.222.132.128:5060 "Noisy feedback tells: pid=26138 req_src_ip=41.222.132.128 req_src_port=33739 in_uri=sip:example.org out_uri=sip:example.org via_cnt==1". .
######################################################
Hi Richard,
here is a patch that should solve the problem. please let my know if I'm right :-) about stability, I would say yes (I no people who are using cpl-c at large scale).
Bogdan
Richard wrote:
Hi,
I tried to use SIP register method to upload cpl script. However I got a result "bad request". The algorithm used in cpled is set as null. I thought normally that it should be md5. The ser's debug message says "Credentials received are not filled properly".
Can someone help me please?
Thanks, Richard
P.S. Has anyone used cpl extensively? Is it reasonably stable?
Index: network/TransportCPLWithSIP.java =================================================================== RCS file: /usr/local/cvsroot/CPLEd/network/TransportCPLWithSIP.java,v retrieving revision 1.7 diff -u -r1.7 TransportCPLWithSIP.java --- network/TransportCPLWithSIP.java 19 Sep 2003 08:23:07 -0000 1.7 +++ network/TransportCPLWithSIP.java 14 May 2004 10:50:34 -0000 @@ -491,6 +491,8 @@ throw new Exception(str_err+""realm" parameter not found"); if (vals[1]==null) throw new Exception(str_err+""nonce" parameter not found"); + if (vals[3]==null) + vals[3]="MD5";
/* comput the authentication */ DigestAuth da;
Hi Bogdan,
It still has the same problem. SER answers back with "bad request".
U 41.222.152.128:33818 -> 41.222.152.128:5060 REGISTER sip:example.org SIP/2.0. Via: SIP/2.0/UDP 41.222.152.128:8700. From: sip:888@example.org. To: sip:888@example.org. Call-ID: 14tg4341-1084556158421-330329-2955420@41.222.152.128. CSeq: 2 REGISTER. Authorization: Digest username="888", realm="example.org", uri="sip:example.org", algorithm=MD5, nonce="40a504aa6954e9a0b09325c2099b4907e94aac4e", qop="auth", cnonce="fc8495a60d285974cf829d", response="84963a6917195ff2a6cae23bfd9cd564". Contact: sip:41.222.152.128:8700. Content-Type: application/cpl+xml. Content-Disposition: script;action=store. Content-Length: 1044.
--- Bogdan-Andrei IANCU iancu@fokus.fraunhofer.de wrote:
Hi Richard,
here is a patch that should solve the problem. please let my know if I'm right :-) about stability, I would say yes (I no people who are using cpl-c at large scale).
Bogdan
Richard wrote:
Hi,
I tried to use SIP register method to upload cpl script. However I got a result "bad request". The algorithm used in cpled is set as null. I thought normally that it should be md5. The ser's debug message says "Credentials received are not filled properly".
Can someone help me please?
Thanks, Richard
P.S. Has anyone used cpl extensively? Is it
reasonably
stable?
Index: network/TransportCPLWithSIP.java
===================================================================
RCS file:
/usr/local/cvsroot/CPLEd/network/TransportCPLWithSIP.java,v
retrieving revision 1.7 diff -u -r1.7 TransportCPLWithSIP.java --- network/TransportCPLWithSIP.java 19 Sep 2003 08:23:07 -0000 1.7 +++ network/TransportCPLWithSIP.java 14 May 2004 10:50:34 -0000 @@ -491,6 +491,8 @@ throw new Exception(str_err+""realm" parameter not found"); if (vals[1]==null) throw new Exception(str_err+""nonce" parameter not found");
if (vals[3]==null)vals[3]="MD5";/* comput the authentication */ DigestAuth da;
__________________________________ Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. http://promo.yahoo.com/sbc/
Hi Richard,
it will be very helpfull for me if you can send me ser output for processing this register (set debug=9 and log_stderror=yes).
Bogdan
Richard wrote:
Hi Bogdan,
It still has the same problem. SER answers back with "bad request".
U 41.222.152.128:33818 -> 41.222.152.128:5060 REGISTER sip:example.org SIP/2.0. Via: SIP/2.0/UDP 41.222.152.128:8700. From: sip:888@example.org. To: sip:888@example.org. Call-ID: 14tg4341-1084556158421-330329-2955420@41.222.152.128. CSeq: 2 REGISTER. Authorization: Digest username="888", realm="example.org", uri="sip:example.org", algorithm=MD5, nonce="40a504aa6954e9a0b09325c2099b4907e94aac4e", qop="auth", cnonce="fc8495a60d285974cf829d", response="84963a6917195ff2a6cae23bfd9cd564". Contact: sip:41.222.152.128:8700. Content-Type: application/cpl+xml. Content-Disposition: script;action=store. Content-Length: 1044.
--- Bogdan-Andrei IANCU iancu@fokus.fraunhofer.de wrote:
Hi Richard,
here is a patch that should solve the problem. please let my know if I'm right :-) about stability, I would say yes (I no people who are using cpl-c at large scale).
Bogdan
-
Bogdan-Andrei IANCU -
Richard