Re: #1024-Fix in switzerland
Le Fri, 16 Oct 2009 11:11:47 +0200, DRSp. it...@gmx.net a écrit : The #1024-fix in switzerland is organized: Art.Nr.Artikel: GTA01-02FIX1024Openmoko GTA01 and GTA02 hardware-fix (Replacing the 10uF capacitor with a new high value 22uF capacitor) Price:42.00 CHF Additional costs: S99943 Versandkostenanteil PDA 19.00 CHF (CH) all prices without MwST. You may order the fix under the aforementioned art.-number. It'll take 1-2 day to perform the fix. SwissIT Repair AG Bahnhofstrasse 50 CH-5507 Mellingen Tel. +41-(0)58 556 01 02 Direkt Tel. +41-(0)58 556 01 01 Auftragscenter Tel. +41-(0)58 556 01 07 Ersatzteilhandel (Fragen zu Bestellungen) Fax.+41-(0)58 556 01 09 Telefax http://www.swissitrepair.ch Info: i...@swissitrepair.ch I'm not related with this company, so direct any question to i...@swissitrepair.ch Thanks ! And about the other fixes as well ? (buzz, bass and GPS / SDIO issue) Best regards -- Alexandre Ghisoli ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-Fix in switzerland
Le Mon, 12 Oct 2009 22:13:05 +0200, DRSp. it...@gmx.net a écrit : dear list, I'm about organizing a #1024-fix-party just without the party-part 'cos there's a IT-firm involved. to get a rough idea about how many FR's are to be fixed, drop a message in this list. cheers itman ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community I'm ! And all other hardware bug (capacitor, ..) Thanks -- Alexandre Ghisoli ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: About the buzz
Le Sat, 31 Jan 2009 15:09:00 -0200, Pablo Miño pablodanielm...@gmail.com a écrit : Community, There is something I do not understand about the buzz. I have 2 chips one for my old carrier and one for my new carrier, they are respectively Claro Uruguay and Antel. With the Claro chip the other person does not listens to the annoying buzz but with the Ancel chip she does. Why could that be? I have a US version of the neo, Claro is supposed to work on 1900 and Antel in 1800. Would that make the difference??? Perhaps where the GSM relay is (near or far away). Maybe if the signal is not good, your freerunner need more output power, and you have the buzz thing. Just an idea, not tested. -- Alexandre Ghisoli ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Pulster fixes (was: Re: buzz fix)
Le mardi 13 janvier 2009 à 09:20 +0200, Christoph Pulster a écrit : Hello, thanks for asking about hardware fixes (I read this list daily). At the moment I'm working out a solution with Openmoko how to handle any repair (buzz SOP, GPS fix etc). In any way I want to offer my customers best service and we try to find a solution which does avoid time-consuming return shipments to Taiwan. Please allow us some days to work that out. Christoph www.pulster.eu Openmoko Shop Thanks for your support. I'll look forward from you on this topic. Count me in as one of the customer that plan to have a FR upgraded if price sound nice. best regards -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How do you like to read a phone number?
Le Mon, 29 Dec 2008 13:00:01 +0100, Michele Renda michele.re...@gmail.com a écrit : Hello to all I would like to know how do you like to read the phone number: I try to explain: when we read a phone number we usually like to separe it with some spaces or signs: for example in Italy when someone give me a mobile phone number I usually write: +39 347 123456 Or if it is a fixed number: +39 02 123456 or +39 011 123456 But I know in USA is more common something like: +1-212-123456 Please, who has some time, can you please write your country (Italy, France, etc.) and the way how usually is normal to read a phone number in your country (with international prefix) The format I use to descrive is this: +39 ### * or +1-###-* (where # replace a char, and * replace all remaining chars) Thank you a lot for your time Michele Renda Hi Michele, It's not so easy, because there are many codes inside a country. For example, switzerland: +41 79 xxx xx xx But for voice boxes : +41 860 xx xxx xx xx Special services +41 [8-9]xx xxx xx xx The idea would be a syntax to allow the country specific need to be applied (aka numbering plan). Best regards -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Swiss numbering plan (was: How do you like to read a phone number?)
Le Mon, 29 Dec 2008 13:37:54 +0100, Michele Renda michele.re...@gmail.com a écrit : Il 29/12/2008 13:26, Alexandre Ghisoli ha scritto: It's not so easy, because there are many codes inside a country. For example, switzerland: +41 79 xxx xx xx But for voice boxes : +41 860 xx xxx xx xx Special services +41 [8-9]xx xxx xx xx The idea would be a syntax to allow the country specific need to be applied (aka numbering plan). Yes, this would be the idea. I am just working on this. I did it for Italian number. and I got very good results. Can you please give me a link to a site where is explained the switzerland prefix list? (if exist) Something like: http://www.comuni-italiani.it/tel/index.html Documents sents off-list. Swiss Gov. agency is OFCOM : http://www.bakom.admin.ch/themen/index.html?lang=en Regards -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How do you like to read a phone number?
Le Tue, 30 Dec 2008 03:04:32 +1100, Carsten Haitzler (The Rasterman) ras...@rasterman.com a écrit : On Mon, 29 Dec 2008 15:34:00 + George Brooke solar.geo...@googlemail.com babbled: On Monday 29 December 2008 14:16:15 Carsten Haitzler wrote: 1234 5678 (call from the 02 area code - i.e. NSW only) I may be wrong but (at least in UK) you don't need to worry about the local version of the number as mobiles need the full version with area code. same in .au - for mobiles, i'm just extending the problem in a generic way to landlines. just illustrating the fun of the system. :) I suggest to work with E.164 numbering scheme only. In this case, you can populate your address book in full international number, without taking care of your location (i.e. don't add prefix when outside of your area / country). Now, it will be useful and really nice to have an presentation number shaper. It will automagically arrange the number you enter or your caller party number in a nice fashion, depending of your local preferences. But remember, today, with VoIP, some operators did not present number according to the ITU or RFC formats. So it will be hard to catch all the possible scenarios. BTW, it's not so hard to detect your operator's country, E.212 specify operators numbers and names, so FR could adapt the rules depending the operator ;) -- Alexandre Ghisoli ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko Om 2008.8 Release
Le vendredi 08 août 2008 à 19:48 +0800, Wolfgang Spraul a écrit : Maybe I should add that the binary Om 2008.8 release is for GTA02 only right now. For GTA01, we have no big plan yet but we will look at it next. The biggest problem that stops us is that we are extremely low on GTA01 phones :-) I am only aware of 1 (ONE) functioning GTA01 in the Taipei office. A bit hard to do development and testing that way. Next week we will look at the Om 2008.8 on GTA01 situation: 1. how many people want this? 2. does anyone in the community step up and compile the distribution for GTA01? (there will be some work: size reduction, GPS chip, etc) 3. can we support or do that from Taipei, do we find enough working GTA01? 4. how much work is it and how fast can we do it? I really like to have the Om2008.08 on my GTA01. -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Switzerland - group order
Hi there, We got more than 10 users saying interrest[1] in GTA02 buying. A list has been setup for thoses who are ready to group order[2]. If I count right, not all the user who are on [1] have added their name on [2]. Please pass the word to let all the users register on the [2] :) Right now I'm not sure about the current status, prices, delays and payement arrangements. Would be nice to get more info from the one who will pass the order ;) [1] http://wiki.openmoko.org/wiki/OpenMoko_Local_Groups:_Switzerland [2] http://wiki.openmoko.org/wiki/GroupSales#Switzerland -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Wireless charger for Neo
Le mardi 01 avril 2008 à 18:19 +0200, Alexey Feldgendler a écrit : Hello! In fact, an open protocol for transfer of electricity over IP has existed since 2002: RFC 3251 http://www.ietf.org/rfc/rfc3251.txt. After DVE (Discrete Voltage Encoding), the electric current can be quickly and securely transmitted to one or more devices over WiFi or Bluetooth in an MPLampS infrastructure. A consumer device can then decode the voltage and use it to recharge its battery. Will OpenMoko, with its openness, be the first to implement MPLampS? BTW, it's 6 years old, same day ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Network Manager
Le lundi 31 mars 2008 à 11:30 +0800, Alex Zhang a écrit : Hi All, As we know, there are many ways to access Internet in GTA02: - wired:usbnet - wireless:wifi, bluetooth - GSM Is there any daemon or framework OM uses to manage these networks as NetworkManager on PC right now? We are developing a portable media device with usbnet wifi support, I am planning to use NM-0.7 or to develop a daemon for managing the networks. Any idea or comments? Sure, it's nice to ear from that kind of project. An feature that would be nice is roaming. Imagine you are using WiFi at home and you are leaving the WiFi range. A warning box could tell you will loose your connection and then open a GMS (GPRS ) connexion to keep it connected. And for business needs, a VPN manager would be very nice (OpenVPN or OpenSWAN IPSEC based). Thanks -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Price of the Freerunner spare parts
Le jeudi 27 mars 2008 à 10:30 -0700, steve a écrit : Yes, The information about returns and defects etc needs to be shared. First, however, it needs to be established or estimated. I haven’t seen a single number from anybody on the demand rate for batteries or LCD or back covers. Anyone care to guess? We provide many mobile DECT phones, and few GSM to very small companies (1-10 ppl) and few bigs (100+). Majors returns are about batteries, nearly 1:1 ratio if customer keep it's device for more than 2years. Second, we have to provide accessories (screen protectors, chargers, holster, sync cable, ...). Third we get few defect (Dead on arrival or misused like falling, got in water, broken LCD and some recall / updates from the manufacturer) and we can fix or change for a new. My guess : - at least 30% batteries in stock, people didn't want to wait to have it changed - get 10-20% accessories and chargers - then a 1-5% for repairs, I think it's the less valued. At least for business customers (most of our market), you'd better have few Freerunner in stock to make a 1:1 change and get an happy customer. You can make the repair in lab then resell the device as reconditioned one. Hope it helps. -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Price of the Freerunner spare parts
Le lundi 24 mars 2008 à 16:00 -0700, steve a écrit : I thought about spare parts a while back. The Issue is this. 1. WHAT do I stock ( which parts) 2. How Many do I stock? 3. How do I sell them to you? 4. What will it cost? 5. how do you get them? I suppose I could Offer component kits for sale. That would be the quickest thing for me to do. Sell the whole bag of parts; fix it your self. or build a business around this service. Hi Steve, As resellers of few products, we always share this information between resellers and the global manufacturer. This kind of risk should be shared between Openmoko and resellers, and they need a good communication to share statistics about returns and defect parts. Now, about shipping, spare parts ordering and cost, you probably need to setup a kind of extranet where the resellers will find the special price, customer's price, qty and where to get them (from a local hub). Best regards -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: freerunner - DONT buy it local
Le jeudi 20 mars 2008 à 13:53 +0100, Matthias Ringwald a écrit : I didn't follow up on all the previous mails, but 399 EURO = 624 USD which looks like a 50 % rip off compared to the mentioned 399 USD here. So I would have to buy it in the US and even get rid of the sales tax.. Same here. The European price is just a joke ! And this site doesn't mention how to pre-order from outside Germany (VAT, special taxes, options, adv kit, ...). This is a really bad sales channel, where you can get your hardware about 50% off if you order in US. I think we (Switzerland) will again get lost and have to pay high prices for such devices :-( -- Alexandre ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Further details of theprocess as we ramp up production of Freerunner
Le vendredi 21 mars 2008 à 00:21 +0800, Sean Moss-Pultz a écrit : Sébastien Lorquet wrote: /me hopes a quick answer from Michael I'm OK to rebuy a PVT prototype, even if it has a defect somewhere :) Just to say I have one of the prototypes ! Sorry we cannot sell these devices. Sean Maybe you can give it ;) Sorry for the list noise, could not resist. -- Alexandre ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko at OpenExpo
Le dimanche 16 mars 2008 à 03:12 +0100, Marco Trevisan (Treviño) a écrit : Alexandre Ghisoli wrote: We have seen the Freerunner working; it's quite fast and responsive with a funny lock screen saying something about an Fruit Phone. No videos for us? :P Heh, sorry, my GTA01v4 doesn't have camera nor video recorder ;) But you can find few video, not the best I've seen : http://www.mefeedia.com/query.php?q=Openmoko%20Openexpo But no freerunner vids. Regards -- Alexandre Ghisoli [EMAIL PROTECTED] YCOM SA ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko at OpenExpo
Le samedi 15 mars 2008 à 09:57 +0100, enaut a écrit : Alexandre Ghisoli schrieb: OpenExpo is a Swiss event about OpenSource. Openmoko was there with a 30 min session with Michael Lauer (right after a session with Alan Cox). We have see the Freerunner working; it's quite fast and responsive with a funny lock screen saying something about an Fruit Phone. The presentation talked about the phone and the new middleware to help development on a simple and powerful interface, based on D-Bus : http://wiki.openmoko.org/wiki/OpenMoko:Dbus_device_API Not so many questions, but was very nice to meet Mickey. but, at this time, there is no slide of the presentation : http://www.openexpo.ch/openexpo-2008-bern/konferenz-programm/ Oh, and last point, session was in German :( Shit why do I always hear about such events after they happened :(. It would have been not too far from home. And I think it could have been very interesting to meet people of the open source movement. greetings enaut Sorry you miss it. In fact, this was annonced (I think on the ML) and it's listed on the event page : http://wiki.openmoko.org/wiki/Current_events And on the Swiss community (arf) page : http://wiki.openmoko.org/wiki/OpenMoko_Local_Groups:_Switzerland Maybe we need a better communication .. Regards -- Alexandre Ghisoli [EMAIL PROTECTED] YCOM SA ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Openmoko at OpenExpo
OpenExpo is a Swiss event about OpenSource. Openmoko was there with a 30 min session with Michael Lauer (right after a session with Alan Cox). We have see the Freerunner working; it's quite fast and responsive with a funny lock screen saying something about an Fruit Phone. The presentation talked about the phone and the new middleware to help development on a simple and powerful interface, based on D-Bus : http://wiki.openmoko.org/wiki/OpenMoko:Dbus_device_API Not so many questions, but was very nice to meet Mickey. but, at this time, there is no slide of the presentation : http://www.openexpo.ch/openexpo-2008-bern/konferenz-programm/ Oh, and last point, session was in German :( -- Alexandre Ghisoli [EMAIL PROTECTED] YCOM SA ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: proprietary firmware
Hi Wolfgang, Thanks for sharing this with the community. Le vendredi 08 février 2008 à 09:32 +0800, Wolfgang Spraul a écrit : Then we ran into problems when bugs were found in the firmware, and we wanted to update handsets out in the field. The vendors would give us firmware updates and reflashing tools, but they wouldn't let us redistribute those tools to our users. We asked for special licenses to allow us to distribute those flashing tools to our users, and got them in some cases, after months of licensing negotiations. Next we discovered that those reflashing tools had further issues: for example, they would only allow loading cryptographically signed firmware into the chipset flash memory. The tools do this because vendors are worried that people would disassemble, patch, and reassemble the firmware, triggering regulatory reclassification of their chipsets (software controlled radio). Madwifi [1] has the same issue with regulatory. Because countries doesn't not allow same frequencies ranges and power output, manufacturer are forced (by laws) to limit hardware possibilities in each countries to pass regulatory tests. In that way, they are very careful to whom they open the firmware updates. Usually, the company that what to use their hardware should sign a very strict contrat where they endorse most of the responsibility. Now, in OpenSource world, this is not possible to endorse that responsibility and let the user change almost all the locked parameters in such way that the device doesn't pass anymore regulatory tests. He suggested we treat any chipset with proprietary firmware as a black- box, a circuit. He suggested we ignore the firmware inside. If the firmware is buggy and the vendor needs the ability to update the firmware, we instead ask the vendor to reduce the firmware to the bare minimum, so that it can be very simple and bug free, and move the rest of the logic into the GPL'ed driver running on the main CPU. This way we completely avoid the issue of distributing proprietary firmware updates and binary firmware updaters with restrictive licensing that load only cryptographically signed firmware. This is probably the only way to get out of the current issues. We liked his advice. It speeds up our decision making and allows us to focus on what we do best: Developing Free Software that is available in full source code, running on the main CPU, that we and anyone else can modify and optimize. There are downsides: We will no longer offer reflashing tools to update proprietary firmware, under any license. For critical firmware bugs, we will accept returns, or in some cases fix the bug in-house. We will push vendors to simplify the functionality of their proprietary firmware, so we can implement more of this on the main CPU as Free Software. Maybe some vendors will even open up firmware for Free Software development, that would be the ideal outcome we are working towards. I can understand the community and OpenMoko point of view here, but what about functionality, speed and power consumption issue ? If you take a look on the recent video acceleration issue with HTC devices [2], there is a clear relation between performances and the firmware (hardware ?) driver. The same issue apply to the current GSM firmware. OpenMoko devices will probably loose a lot of their functionality because of moving everything in CPU area. What are the possibilities ? I dont know, but forcing vendors to let OpenMoko updates their phones are not a viable option, unless you can let some trusted resellers around the world to make it for free. Making a dual licensed phone ? One closed with everything in firmware (so, easy to use, fast and low consumption, maybe re branded ?) and a true OpenSource phone that will probably not compete (in term of speed and power consumption) with the 1st one ? [1] http://madwifi.org/ [2] http://htcclassaction.org/whattodo.php -- Alexandre ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: France : Taxes for video and mp3 playing capacity / Switzerland too
Le vendredi 25 janvier 2008 à 10:37 +0100, Steven Le Roux a écrit : On Fri, 25 Jan 2008 10:16:37 +0100, Etienne Labaume [EMAIL PROTECTED] wrote: Selon Steven Le Roux [EMAIL PROTECTED]: No direspect or anything but that's probably the dumbest tax I've ever heard of. Probably France is the dumbest country right now about taxes and other stupid stuff... Yeah, almost every tax talked about in this thread exists in France. But how do we avoid the Neo to be taxable ? As said, if you don't sell the phone with an embedded player, I think the neo become out of conditions to be taxed. At least, you can justify that you are buying a phone and nothing else. To jump on this topic, Switzerland has recently adopted the same. Since audio tapes, we still stick on a (low) taxes on recordable media (CD, DVD, tapes, ..) and last year, we got taxed on the MP3 players. They was talking about HDD too ... :( -- Alexandre Ghisoli [EMAIL PROTECTED] YCOM SA ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Power Management on Neo1973 - kernel 2.6.24
Le jeudi 10 janvier 2008 à 22:40 +0100, Tim Niemeyer a écrit : Today, i played a bit with power measurement and standby. It was very surprising, and the actual power was very different from time to time. Sometimes neo booted and did draw about 400mA in idle. Sometimes only 280mA. In Standby mode it was exacly the same, but most the time it tooks ~80-95mA. Sometimes only 65mA! One time the neo did draw only about 20mA! Don't know what was different: booted - standby - 20mA! I think this 20mA was drawn by the GSM. Just to add on this topic, kernel 2.6.24 (tested -rc7) is really power saving. On my laptop and 2.6.23.9, I cannot go under 9.7W while LCD power on and laptop turned on. With 2.6.24-rc7, I can goes down at 6.5W ! It seems that kernel has really nice power improvement ! And of course HPET and dynamics ticks are required to wake up CPU less often. And my tests showed the sound card eat 0.5W. The new AC97 path allow standby when not used. --alexandre ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Product naming / wiki page naming / restructuring
Le vendredi 27 juillet 2007 à 18:24 +0800, Harald Welte a écrit : So, we will have Neo1973-1.0 = GTA01 Neo1973-2.0 = GTA02 well, please don't add numbers like 1.0/2.0, since that would just lead to further confusion. I really think it makes sense to use one naming scheme, and don't differentiate between 'inside the company' and 'outsid the company' Strongly agree, but in the other hand, hardware naming should be simple enough to let people understand what devices they got. Let see other mobile product, they have brand, model and version (numbers). GTA01 is quite hard to remember, but could do the trick. For example, Palm got different hardware base (Zire, Tungsten, ...) and numbers (Zire 31/71/22, Tungsten T3/E3, ...). So hardware base models and revisions should have clear and simple naming scheme that let user know what devices they buy (and what they got inside). OpenMoko-0.5 or whatever scheme is already in place. -2007 and -2008 so far. We might have 200x.y at some point. If you take a look on PalmOS, I always hated that I cannot install my PalmOS version X.Y to my device, because it's only for new hardware. AFAIK, there will be only one software name for all (future) Neo devices, so how to name it and understand that you need *minimum* version 2008.0 to use with your device (for example) ? And the opposite, could you upgrade your Neo1973 GTA01v4 with the OpenMoko-2009.2 ? Each phase can also get a consumer-friendly nickname. Well, there only is one phase in which consumers get involved: phase 2. What does it mean about revision and software naming ? Did you plan to have developer and user naming scheme ? This can be harder to implement, but probably easier to follow from a normal user (read non developer). As you said before, have a clear naming convention will help to organize stuff like documentation, wiki, filesnames and so on. Best regards -- Alexandre ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Missed call communication protocol
Le mercredi 07 février 2007 à 16:08 +0200, Rodney Arne Karlsen a écrit : Hi there While you can choose your callerID when using a sip server, it may not stay the way you set it once it passes through the PSTN gateway. I tried playing with CallerID stuff some time back here in South Africa and our PSTN provider will only allow you to set your caller ID to a number that is assigned to the line you are using. If you are lucky enough to have a PRI line then you start with around 100 numbers. Sorry to throw a spanner in the works but I'm not sure that this will work here. It may work in other countries. I think I heard about it working in the US. I'll second that for switzerland. When you subscribe for a E1 channel or direct VoIP trunk, you cannot send full e.164 number, but only the last digits that stick in the range of number the telco gave (rent ?) to you. There are some supplemental services, like Special Arrangement (SA), that let you send full numbers, without controlling from the telco side if you stay in your range (in fact, your real number still sent on the network, but a supplemental field is added with the number you want to show). Now, for law enforcement, you are *NOT* allowed to change your clip on the network. To solve this issue, I see 2 directions : 1/ Ask for a SS7 trunk, to get more powerfull abilities (cell localisation, supplemental services, direct access to radio, ...) but telco will charge you for that, and a big access fee :( Also you need a SS7 endpoint. 2/ For ISDN network (Q.931 signaling), use of the UserInfo field, on the signaling session (yes, you can send some byte when the phone is ringing, without charge) Probably for all European countries this will be the same. ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: Missed call communication protocol
Le jeudi 08 février 2007 à 11:16 +0100, Richard Bennett a écrit : 2/ For ISDN network (Q.931 signaling), use of the UserInfo field, on the signaling session (yes, you can send some byte when the phone is ringing, without charge) Ok... Are you sure you don't mean the 'Display' field in the ISDN SETUP message? I can't find references to a UserInfo field in q931. http://www.cotse.com/CIE/Topics/126.htm Yes, this is the DISPLAY (sorry for the confusion, INFORMATION is a message itself). Apparently the Q.931 protocol limits the maximum length of the Display Field information element to 44 octets, that should mean one can use 44 characters for a message without opening the line, which would be fine. ITU spec say 2 bytes minimum, up to 34 or 82 bytes, depending of the network (should be national specific ?) It seems that GSM should support the full range of ISDN messages, http://kbs.cs.tu-berlin.de/~jutta/gsm/js-intro.html so I'm wondering, why is no one using this for enhanced caller-ID, or similar applications. Where's the catch? I was working on a project, maybe 15 years ago, where we developped a modem to transfer data : 1/ during setup, for free 2/ during the blanks of a conversation (approx 80% of the time, because only one speaks at time, so you got a free 64kbps channel :)) This takes not very long until telco notice the D channel trafic, and since then, they charge for alerting, even if no answer (maybe 10% of unanswered call) to cover this trafic costs. Not sure about now, if this still a used (i'm not working anymore on low level communications). So, second part was to cut additional messages (SETUP DISPLAY) between network (aka roaming or international call). This need a more deeper test, but IMOO, this *could* be working on some networks, and probably not on some other. Now, about GSM networks and Gateways, I really dont know if this is a 1:1 passtrough .. --Alexandre ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
