Re: MSISDN info
No, problem anywhere in RADIUS-Kannel config see my kannel logs: 2003-09-30 16:44:23 [1] INFO: RADIUS: Got data from NAS 10.10.5.254:21704 ... 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Authenticator (md5) is:: 2003-09-30 16:44:23 [1] DEBUG: Octet string at 130290: 2003-09-30 16:44:23 [1] DEBUG:len: 16 2003-09-30 16:44:23 [1] DEBUG:size: 17 2003-09-30 16:44:23 [1] DEBUG:immutable: 0 2003-09-30 16:44:23 [1] DEBUG:data: 46 72 71 09 99 49 7a 28 10 3e e1 0c f0 5c fa 5c Frq..Iz(\.\ 2003-09-30 16:44:23 [1] DEBUG: Octet string dump ends. 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (44) `Acct-Session-Id', len 8: 0033FDED 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (7) `Framed-Protocol', len 4: 1 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (8) `Framed-IP-Address', len 4: 172.16.188.2 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (26) `Vendor-Specific', len 33: 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (45) `Acct-Authentic', len 4: 1 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (1) `User-Name', len 3: wap 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (40) `Acct-Status-Type', len 4: 1 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (31) `Calling-Station-Id', len 11: 7xx 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (30) `Called-Station-Id', len 10: xx 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (26) `Vendor-Specific', len 15: 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (5) `NAS-Port', len 4: 359 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (61) `NAS-Port-Type', len 4: 0 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Unknown attribute type (0x04d) len 25 in PDU `Accounting_Request'. 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (6) `Service-Type', len 4: 2 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (4) `NAS-IP-Address', len 4: 1.1.1.1 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Attribute (41) `Acct-Delay-Time', len 4: 0 2003-09-30 16:44:23 [1] INFO: RADIUS PDU type: Accounting_Request 2003-09-30 16:44:23 [1] INFO: RADIUS: Mapping `172.16.188.2 - 79289874072' for session id 0033FDED added. / FORWARD DATA to RADIUS */ 2003-09-30 16:44:23 [1] INFO: RADIUS: Got data from remote RADIUS 1.1.1.3:1813 2003-09-30 16:44:23 [1] DEBUG: Octet string at 131d58: 2003-09-30 16:44:23 [1] DEBUG: len: 20 2003-09-30 16:44:23 [1] DEBUG: size: 21 2003-09-30 16:44:23 [1] DEBUG: immutable: 0 2003-09-30 16:44:23 [1] DEBUG: data: 05 d9 00 14 a1 2b 54 d0 0e f8 a1 68 95 d9 55 09 .+Th..U. 2003-09-30 16:44:23 [1] DEBUG: data: c9 28 a5 f6 .(.. 2003-09-30 16:44:23 [1] DEBUG: Octet string dump ends. 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Mapping table contains 1 elements 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Session table contains 1 elements 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Client table contains 1 elements But I do not see that in RADIUS logs!!! It very strange! (and mobile station did not autorize :(() Can I see any success story (with configuration samples)? Many, many thanks for your help! :) I had problems with framed-ip-address on cisco, so i've added following lines cisco aaa and radius config: radius-server attribute 8 include-in-access-req aaa accounting delay-start Please try. Yury Mikhienko wrote: Can you show me your kannel and radius configs? FreeRadius using as RADIUS server The kannel is set as RADIUS client in RADIUS config Kannel configs: group = radius-acct nas-ports = 210 our-host = 1.1.1.1 remote-host = 1.1.1.2 secret-nas = naspasswd secret-radius = naspasswd unified-prefix = +7928;7928;8928;928 BTW, which nas you're using? Cisco AS5350 Problem in following: kannel did not FORVARD pocket to RADIUS RADIUS seems to be configured properlly, but it does not any packets from kannel :(( check if your radius is configured to accept packets from radius. -- Best regards, Yury Mikhienko. IT ERP group head, ZAO Mobicom-Kavkaz
RE: Force WML error on HTML content
If you are controlling the http server that content is withdrawn from, you can use the ErrorDocument (apache) directive to set it to w WML source. If the http server is foreign, then this is really an error in the http server setup (though a very common one). Converting / replacing html pages with wml is typically NOT what a gateway does (against the specs) but with some modifications Kannel, it could be done. -- Rene... -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Rene VellekoopSent: woensdag 1 oktober 2003 13:30To: [EMAIL PROTECTED]Subject: Force WML error on HTML content Hi, Is there a way to show people an WML error when they try to access HTML pages through the kannel gateway? The problem is we provide a dialin service but the call gets dropped as the phone doesnt recognize the first pages content type. We rather sent the user to our main page or something. Thanks! Rene Vellekoop DAC Planet BV - Rotterdam - +31 (0)10 4799700 [EMAIL PROTECTED] - http://www.dac-planet.com
Kannel Character set issue GSM-Latin appears to run TWICE!
hey guys, I must be doing something silly in my kannel use/config. However, this is what happens: When I send from a handset to my operator assigned shortcode the character @, it comes to kannel and I see the message in the kannel.log debug output as being of hex value '00'. When it reaches kannel's access.log, it is now showing up as an inverted exclimation mark. It is also passed onto our web service as an inverted exclimation mark. At first I was confused by this mapping, but a quick look at how a GSM - latin conversion works, one realizes that Kannel appears to be converting the data TWICE. 00 in GSM to latin1 == decimal 64 (the @ symbol). 64 in GSM to latin1 == decimal 161 (the inverted !) A similar problem seems to be occuring when I use kannel to send to my handset. In order for an @ symbol to appear on the handset, I need to send it decimal 161, as it appears to go from latin1 - gsm twice. What can I do to alleviate this? Thanks, Bryce
questions about udh for ringtones
I would like to send ringtone via SMS data, i know the udh %06%05%04%15%81%00%00 short ringtone ( 1sms) but what is the udh for long ringtone (2 or 3 sms)? The question is for nokia smart message. A second question is about imelody, is it possible to send imelody ( alcatel, ericsson-sony 's format) via kannel ?
RE: Kannel Character set issue GSM-Latin appears to run TWICE!
My mistake... It appears that the SMSC we're connecting to is sending/receiving data to us as LATIN characters (except the GSM extended characters). They're also declaring the data_coding to be 0, which I believe is indicative of the 7bit GSM alphabet. Kannel performs a GSM-Latin conversion (and a Latin-GSM conversion when sending TO the SMSC) and thus the double conversion. Is there a way to tell kannel not to do that conversion? I'm using 1.3.1 development version. Many thanks, Bryce -Original Message- From: Bryce Pasechnik Sent: Wed 10/1/2003 9:35 AM To: [EMAIL PROTECTED] Cc: Subject: Kannel Character set issue GSM-Latin appears to run TWICE! hey guys, I must be doing something silly in my kannel use/config. However, this is what happens: When I send from a handset to my operator assigned shortcode the character @, it comes to kannel and I see the message in the kannel.log debug output as being of hex value '00'. When it reaches kannel's access.log, it is now showing up as an inverted exclimation mark. It is also passed onto our web service as an inverted exclimation mark. At first I was confused by this mapping, but a quick look at how a GSM - latin conversion works, one realizes that Kannel appears to be converting the data TWICE. 00 in GSM to latin1 == decimal 64 (the @ symbol). 64 in GSM to latin1 == decimal 161 (the inverted !) A similar problem seems to be occuring when I use kannel to send to my handset. In order for an @ symbol to appear on the handset, I need to send it decimal 161, as it appears to go from latin1 - gsm twice. What can I do to alleviate this? Thanks, Bryce
