Re: Wireless Profiled TCP
Yes, WAP 2.0 is based on it. Aarno On 23.12.2003, at 11:36, James Wong wrote: Hi all, Has the standardization for the Wireless Profiled TCP completed? James
Re: [Q] NewNet SMCI support in Kannel ?
> Is it already planned in Kannel project? no. At least I'm not aware of such an SMSC protocol. > Or, is there anybody who knows the specification of SMCI ? no. Same again. > I am trying to implement SMCI. ;-) if it's TCP based and if you have a full specification to your hand, then addopt the SMSCConn abstraction layer and it's smsc_foobar module API to write an "smsc_smci.c" module. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Re: Wireless Profiled TCP
I have tried to download the specs from the wapforum website but the server asks for a login/password. I do not recall having this problem when I last downloaded the past version a few months ago, has something changed? Thanks, Marco
Re: Wireless Profiled TCP
Marco Fassiotto wrote: > > I have tried to download the specs from the wapforum website > but the server asks for a login/password. I do not recall > having this problem when I last downloaded the past version > a few months ago, has something changed? check the "new home" of the WAP specs at OMA. http://www.openmobilealliance.org/ Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Re: Wireless Profiled TCP
Stipe Tolj wrote: Marco Fassiotto wrote: I have tried to download the specs from the wapforum website but the server asks for a login/password. I do not recall having this problem when I last downloaded the past version a few months ago, has something changed? check the "new home" of the WAP specs at OMA. http://www.openmobilealliance.org/ By the way, am i just looking into a wrong place, or all the specs are rebuilt by OMA from scratch? http://member.openmobilealliance.org/ftp/Public_documents/ Here, i can only find *-OMA-* docs, and , omfg - they are also all .DOC now... Are they nuts? :( What happened to good old PDF and the whole set of the specs made by wapforum? :( Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Re: Wireless Profiled TCP
Konstantin Vayner wrote: > > Here, i can only find *-OMA-* docs, and , omfg - they are also all .DOC > now... > Are they nuts? :( > What happened to good old PDF and the whole set of the specs made by > wapforum? :( refer to: http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html where you'll find all the WAP forum docs. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Re: GSM 03.38 packed data in SMPP messages
Hi We have come across such a beast, and decided that it was indeed non standard and not conforming. We did make a patch for this unamed provider - but we dont use them anymore so I dumped the patches. But yes basically we just pulled the code from the AT module Nisan - At 11:39 PM 2003/12/26, Benjamin Lee wrote: I, also, haven't come across any SMSC's using packed GSM03.38 encoding, only 7 bit GSM03.38 transported in 8 bit octets. http://www.mail-archive.com/[EMAIL PROTECTED]/msg00099.html On Friday, 2003-12-26 at 10:40:39 PM, Ian Cass scribbled: > Rafael 'Dido' Sevilla wrote: > > > The SMPP SMSC made by ZTE (http://www.zte.com.cn) apparently sends and > > expects to receive GSM SMS text packed in that way, oddly enough. Does > > SMPP 3.3/3.4 say that it should be received unpacked or packed? Don't > > have the specs on hand... > > Well, section 4.4 submit_sm says that a short_message is field type Octet > String. Section 2.11 defines this as "Octet String A series of octets, not > necessarily NULL terminated". 7bit characters are not octets, they are > septets. However, you could argue that by packing them, you are transferring > them as octets thereby fulfilling the spec. > > Having said that, SMPP does not define any method to tell you that the data > is in fact packed. Section 5.2.19 data_coding *is not* the GSM DCS field > even though most SMSC's use it as such. SMPP uses data_coding merely as a > character set indicator & breaks other functions of GSM03.38 DCS out into > other fields. SMPP data_coding does not allow for indication of packed data > & there is no other field available to indicate that the data is packed. Are > ZTE treating the data_coding field as GSM DCS & setting the packing bit? > > Strictly speaking, packed text is not allowed in SMPP. I don't know of any > other SMPP SMSC that does this by default. > > -- > Ian Cass > -- Benjamin Lee Melbourne, Australia "Always real."http://www.realthought.net/ __ I used to think that the brain was the most wonderful organ in my body. Then I realized who was telling me this. -- Emo Phillips
Re: Debugging logs
"J.Mohamed Zahoor" wrote: > > Hi all > I want to dump debug mesages when an sms reaches our smsbox from > an SMSC through the bearerbox. > I tried starting smsbox with the following option, but in vain. > "smsbox -v 1 -D "sms" smskannel.conf" > I want to see all the debug messages in the code which is of the > form > "debug(sms " > What is wrong... iam i starting the smsbox with correct arguments..?? > Please enlighten.. is your smsbox config group has a log-file config directive and log-level = 0 set, then all debug() messages will be logged there. Your invocation call causes to dump log in level 1 which is info() and higher to stderr. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
