Skip to Content.
Sympa Menu

sip.edu - Re: [sip.edu] Weekly SIP.edu Call Today

Subject: SIP in higher education

List archive

Re: [sip.edu] Weekly SIP.edu Call Today


Chronological Thread 
  • From: Stephen Kingham <>
  • To:
  • Subject: Re: [sip.edu] Weekly SIP.edu Call Today
  • Date: Thu, 27 Jan 2005 20:55:10 +1100

Hi Dennis, et al

I have all the best intentions to attend these meeting, only I often choose to stay asleep instead due to the timezone change ;-).


Anyway I wanted to report that Quincy Wu and I gave a 1 day SIP Tutorial at the 19th APAN Meeting in Bangkok with 20 attendees, the SIP.edu project was a part of that. It seamed well received and there is a lot of interest in SIP in APAN, much more that H.323.

For example Sri Lanka looks like a real possibility of sip.edu.


One major issue is how to route E.164 calls. I know this is out of scope of sip.edu but please allow me to mention it here considering your success in sip.edu routing.
Several APAN Members (I am one) are looking at
-ENUM
-TRIP
-as well as a hierarchy of SIP Redirectors with static entries as a short term solution.

In APAN H.323 and the E.164 routing using GDS has not taken off, but there looks like a real possibility we could get E.164 routing using SIP.


Please forgive me for raising E.164 routing here, I realise there are other appropriate mailing lists.

Regards

Stephen Kingham


Dennis Baron wrote:

Call today, Thursday, 1/20/05 2:00-3:00 EST (UTC-5)

*** Note that the dial-in phone numbers have changed since last year. ***

Agenda

- Minutes from last meeting - see below - any corrections?

- Deployment updates, issues, questions

Michael Van Norman from UCLA is going to try to join us to talk
about their SIP.edu deployment. And bring your updates and
questions!

- Possible SIP.edu Workshop at Spring VON Conference

Results of the survey and discussion

- Update on the Cisco GSM CODEC Problem - Dennis

- SIP.edu Peering - By the Numbers - Dennis

I'd like to revisit the topic we discussed in the fall -
specifically the idea of peering with "open" SIP service providers.
What are the possible service models? Who would operate a central
service? Are there funding opportunities? A copy of my slides from
the last discussion are here:

http://mit.edu/sip/sip.edu/presentations/np110.pdf

- As always, let me know if you have any other items for this or
future agendas!

Dennis

Thursday 2:00 PM US/Eastern (UTC-5)
To join the call, do one of the following:
a. Dial +1-734-615-7474, or
+1-800-392-6130, or +1-866-411-0013 and enter access code 0153458, or
b. Call
sip:,
or
c. To have the system call you, click here:
https://edial.internet2.edu/call/0153458

--------

SIP.edu Conference Call January 06, 2005

*Attendees*

Dennis Baron, MIT
Candace Holman, Harvard
Tim Bastian, Penn State
Arthur Gaylord, Woods Hole Oceanographic Institution
Bruce Mazza, Avaya
Yul Pyun, University of Hawaii
Jeff Kuure, Internet2

*Discussion*

Today's SIP.edu conference call focused on Harvard's SIP
implementation. Candace Holman discussed the university's Avaya-based
strategy, running on Linux, and using LDAP integration based on Columbia
University's LDAP plug-in. Currently the extended features of the software
remain unexplored, as some rough edges in the base configuration are
being ironed out.

Some of the difficulties involve getting devices to register with the
system - some devices simply won't register. Consulting the log files
has been problematic in terms of locating and parsing them as an end
user. In addition, LDAP queries behave unexpectedly when multiple phone
numbers are returned for a single email address. Harvard, unlike MIT,
has lists of numbers associated with some email addresses, and options
for return results for these cases are being discussed. Possibilities
include returning no values, or multiple values either in a list or
prioritized in some format. No participants in this call know offhand
what the RFC specifies for multiple results. Harvard is currently
testing all possible cases for email addresses associated with zero,
one, or several phone numbers. Finally, email addresses or URIs are the
preferred format for SIP calls as the proxy maintainers have no control
over the campus phone numbers.

The call ended with discussion of the upcoming SIP workshop to coincide
with the VON conference in San Jose on March 7. Originally a two-day
workshop, beginning on Sunday March 6, was mentioned but no space is
available until Monday. There are VON events scheduled on Monday,
but this day and evening are mostly free for VON participants. As
there have been several successful implementations since last year,
call participants expressed interest in seeing unique implementations
or ones that focuses on specific platforms. In addition, presentations
on SIP scalability and multiple campus setups were desired. Volunteers
for a program committee are welcome.

The next call will be on Thursday, January 20th.


--
Stephen Kingham, MIT, BSc, E&C Cert
Project Manager and Consulting Engineer mailto:
Telephone +61 2 6222 3575 (office)
+61 419 417 471 (mobile)
sip:

Voice and Video over IP
for The Australian Academic Research Network (AARNet)
http://www.aarnet.edu.au





Archive powered by MHonArc 2.6.16.

Top of Page