Hello Jan, JJ> It is correct. So I can go on, it seems me .... JJ> phplib_id is a unique key for the php library (used by serweb). Is that used by the server ? is the only data that I can't write using ODBC from a Windows pc. JJ> ha1 contains an MD5 hash of username domain and password. You can use JJ> gen_ha1 utility to generate it. ha1b is the same only the username is JJ> in form username@domain. JJ> ha1 and ha1b columns are used only if you have calculate_ha1 JJ> parameter of auth_db module off. That's not my case .... I would like to ask another question to everyone involved in SER: I'm experimenting with Grandstream IP Phones, that are allowing only numbers for calling out. That'is a big problem when you want to call someone outside your domain .... for instance 11111111(a)iptel.org I think that the right way to handle this situation is to use a numeric prefix for every domain that our ser proxy should convert to domain names for uri rewriting. Finally the question: Is a prefix/domain standard conversion table avalaible somewhere ? something like ... addline 1-747-474 (real prefix, I guess). Again, tnx ! -- Best regards, Alessio mailto:alessiof@interconnessioni.it

Hello Jan, JJ> Check out pdt module (prefix to domain translation). I'm missing that, is it in the standard 8.11 rpm ? -- Best regards, Alessio mailto:alessiof@interconnessioni.it

Hello Jan, Monday, November 10, 2003, 5:06:16 PM, you wrote: JJ> No, the module is not included in the rpms. You will have to compile it JJ> from sources. got it, no way to build it without rebuilding all SER, right ? -- Best regards, Alessio mailto:alessiof@interconnessioni.it

On (10.11.03 16:20), Alessio Focardi wrote: You are asking for the VoIP equivalent of the hosts file. Those files have been obsoleted long ago, and i'm pretty sure that prefix lists will not have much chance in the long run, too, because: There is already a DNS based number-to-URI lookup protocol/mechanism: ENUM For example, my phone can be reached by doing an ENUM lookup for the E.164 number "+4359966366001" which, from the DNS point of view, looks like: graham:~# host -t NAPTR 3.0.0.6.6.3.6.6.9.9.5.3.4.e164.arpa. 3.0.0.6.6.3.6.6.9.9.5.3.4.e164.arpa NAPTR 100 10 "u" "E2U+sip" "!^.*$!sip:e001-366003@enum.at43.at!" . SER features a module which can be used to do call routing using ENUM. cheers axelm

On (10.11.03 16:42), Alessio Focardi wrote: sorry for my ignorance, E.164 is the ITU-T recommendation for the format of phone numbers. So, an E.164 number is simply a phone number. If you're talking about ENUM entries: You would need to have phone numbers for your users plus a ENUM DNS infrastructure in your country. If you have already a phone number, you could give your users extensions behind that number. Unfortunately, there is no ENUM trial going on in Italy yet, so you won't be able to publish ENUM records for your users in the public DNS in that case, so other users would not be able to find your users via ENUM. But, you could still use ENUM for finding other ENUM users, a currently small, but rapidly growing community. You won't need to keep a "prefix to domain" list for all the other VoIP providers, and your users won't have to remember "which prefix to dial for which provider?" to see a rough sketch how it works, take a look at our presentation at http://enum.nic.at/documents/AETP/Presentations/Austria/0017-2003-07_ENUM-D… I'm happy to supply you with more detail in private mail, i consider that being already quite off topic on the SER users list. Feel free to contact me. cheers axelm

Hello Alexander, so, if I'm getting it right: I have 2 possibilities now: use "prefix to domain" rewriting there is a ser module for doing that, but in my opinion it looks pretty lame to keep up to date the association between prefix and phone numbers; when you will have 2.000.000 sip domains who is going to save you ? :) That's the reason why I was asking for a centralized prefix/domains translation table: its seems obvious to me that if everybody is going to decide is own associations things are going to be very funny in a few. use the "ENUM" method That's something like a "dns of phone numbers/sip domains" that's also compatible with the pstn numbering plan for better integration. You resolve the "fake pstn" phone number to obtain a SIP address, complete with domain. The only problem could be that you dont have to remember SIP addresses but very long phone numbers .... :) Am I on the right way to undestand the matter ? Beside this I'm wondering why Italy is out of this interesting ENUM trial ... no one was willing ? Maybe you have find someone here ! :) Monday, November 10, 2003, 5:05:08 PM, you wrote: AM> On (10.11.03 16:42), Alessio Focardi wrote: AM> sorry for my ignorance, E.164 is the ITU-T recommendation for the format AM> of phone numbers. So, an E.164 number is simply a phone number. AM> If you're talking about ENUM entries: AM> You would need to have phone numbers for your users plus a ENUM DNS AM> infrastructure in your country. If you have already a phone number, you AM> could give your users extensions behind that number. AM> Unfortunately, there is no ENUM trial going on in Italy yet, so you AM> won't be able to publish ENUM records for your users in the public DNS AM> in that case, so other users would not be able to find your users via AM> ENUM. AM> But, you could still use ENUM for finding other ENUM users, a currently AM> small, but rapidly growing community. You won't need to keep a "prefix AM> to domain" list for all the other VoIP providers, and your users won't AM> have to remember "which prefix to dial for which provider?" AM> to see a rough sketch how it works, take a look at our presentation at AM> http://enum.nic.at/documents/AETP/Presentations/Austria/0017-2003-07_ENUM-D… AM> I'm happy to supply you with more detail in private mail, i consider AM> that being already quite off topic on the SER users list. Feel free to AM> contact me. AM> cheers AM> axelm -- Best regards, Alessio mailto:alessiof@interconnessioni.it

AM> Well, people are already used to remember/keep numbers. It simply AM> depends. I'll probably print sip:axelm@nic.at43.at on my business card, AM> but i'll put +4359966366003 into my mobile phone. Every answer rises a question :) Lets imagine 2 situations: someone is calling you from pstn, he rings your number, your pbx directs the call to your desk. Thats plain old telco style, even if you have an ip pbx. Then I compose your number in my grandtec phone, my server is configured to ask for the translation of your number to a SIP address using ENUM. The "central authority" resolves the number because he knows that "+435996636" is "nic.at43.at" phone, and 6003 is the extension of "axelm". Thats looks a lot like "lcr" with autofallback, user EVERY time someone calls out from an Ip PBX or SIP server, great stuff. BUT: I checked and it looks like +878 is the "international prefix" for IP telephony. What is it for if you are using your usual phone number ? Maybe for "pure ip" services, no pstn at all ? Thank you, I'm more involved into this now .... AM> yep, you're perfectly on track. AM> I'm currently not aware of the activities in Italy. I'll try to find AM> out, please stay tuned. Tnx, it looks very interesting, by the way I'm tryng to steer my company to this field very soon. AM> cheers AM> axelm -- Best regards, Alessio mailto:alessiof@interconnessioni.it

AM> oops, i forgot to mention, my phone is reachable by dialing AM> +878102843366003 as well ;) your business card is becoming a little oversized, isnt'it ? :) AM> +878 could, for example, be an option for people who currently don't AM> have an ENUM trial active in their country... got it? On to the pratical question: I want to launch a free sip directory here in Italy. what could be the next logical step to that my numbering plan will be coerent to future scenarios ? I'm going to assign every user a 6 digits username, that's pretty plain. Beside this, I'm pretty confused: sipphone.com states that his prefix is 1-747-474, so if they are not partecipating in ENUM it seems logical to me to use uri conversion to append "(a)sipphone.com" to every number that begins with "1-747-474". What for addaline.com that does not state any prefix ? I have to choose one that I like ? And for my future plans ... Do I have to apply now (if possibile) for an +878xxxx prefix or I can just invent one, hoping that when they will become public avalaible I will retain mine? In this case .. how many digits will xxxx be ? Again, tnx, If you will ever come to Florence you will have someone to show you the city ! :) -- Best regards, Alessio mailto:alessiof@interconnessioni.it

At 04:20 PM 11/10/2003, Alessio Focardi wrote: There is the pdt module which can handle the prefix-to-domain translations for you. There is a small webpage too which allows you to ask to query domains and get existing or newly generated prefixes for them. --jiri

Greg, On 10-11 10:12, Greg Fausak wrote: Currently there is no cache for subscriber table, so it can be updated directly. Location and domain tables are cached. Subscriber table is uncached right now. The possibility to disable cache for location table will be included in the next release. Jan.

Greg, On 10-11 10:44, Greg Fausak wrote: No, subscriber table has never been cached. ETA is middle of January. I wouldn't recommend unstable stuff right now because it contains many untested changes. Jan.

On 10-11 11:12, Greg Fausak wrote: That was probably location table (serctl ul add) Jan.