L10 / 01
Something you can use on Monday
Every speaker leaves you something practical: an architecture, a lesson, a code example or a deployment checklist. Not just an opinion.
Technical UC meetup LAYER10: SIP Share Ideas & Perspectives.
Less pitching. More teaching.
A community-led afternoon of short talks, live demos and honest lessons across UC, voice, contact centre, AI and CPaaS. Up to a hundred people, subjects chosen by members, and drinks to finish.
Somebody has already
solved your problem.
Come and watch them
show you how.
Learn from people who have actually done it, and share what you have learned yourself.
Open to the whole technical community, vendors included, as long as they come to teach.
- Enterprise IT professionals
- UC and voice engineers
- Contact centre and CX specialists
- AI and CPaaS developers
- Partners and vendors who teach
Sound familiar?
What people
told us they wanted.
We asked the community what makes an event worth a day away from work. These are the answers that shaped Layer10:SIP.
“Show me what you built, what failed and what changed as a result.”
“Deep dives at a proper technical level, not another introduction to the basics.”
“Demos instead of slides, and something I can use the next day.”
That is the whole brief for every SIP speaker.
What you leave with
L10 / 02
The honest version
What worked and what did not, from the people who ran it, including the parts that never make it into a case study.
L10 / 03
People worth following up with
The speakers stay for the drinks, and so does everyone else who came for the same subject. The conversations after the talks are half the point.
Is this one for you?
Come to a SIP if…
- You learn more from a working demo than from a product deck.
- You have built something worth showing, or want to see how somebody else built theirs.
- There is a subject you would like somebody to explain properly.
Nominated by members
Requests like these
- We have been struggling to integrate voice AI agents into our contact centre. Can somebody show us how they did it?
- Has anyone moved from Direct Routing to Operator Connect without disrupting users? I would love to see the plan.
- Show us a real-time transcription and summary pipeline that is actually in production.
- How is everyone handling emergency calling for hybrid workers on Teams Phone?
- We built our own CPaaS notification service. Happy to demo it and take questions.
- Can somebody explain resilient SBC design in plain English?
- Nominate a subject →
What it is
Talks, demos and
honest lessons.
A small, community-led technical event for people across UC, voice, contact centre, AI and CPaaS. The subjects come from members, the speakers come to teach, and nobody can buy a slot.
100
Attendees, at most
5
Kinds of session
6
Hours, talks then drinks
0
Speaking slots for sale
Scale
A hundred at most
Big enough for a good mix of people, small enough that you can find the speaker afterwards and carry on the conversation.
Content
Practical, not promotional
Live demos, real deployments and honest failures. If it could be a sales deck, it is not a SIP talk.
Social
Drinks to finish
The sessions end at 4:35pm and the networking runs until seven, in the same place.
The practical bit
- When
- 1:00pm to 7:00pm: sessions until 4:35pm, then networking drinks
- Size
- Up to 100 people, with no more than three from any one company
- Ticket
- £100 per person, maximum three per company
- Who
- The open technical community across UC, voice, contact centre and CX, AI and CPaaS
- Subjects
- Nominated and voted on by members
- Speakers
- Practitioners, partners and vendors with genuine technical substance. No paid slots
- Backers
- Community Benefactors, Founding Benefactors and the sponsors of each SIP can send one person each to take part
- Venue
- Space to present, with a bar to move on to afterwards
What happens at a SIP
Five kinds of session.
None of them a pitch.
L10 / 01
10 min
Lightning talks
Short, sharp talks on one idea each. Three in a row, three different perspectives.
L10 / 02
25 min
Show and tell
Live demonstrations of real projects, running for real rather than in a demo environment.
L10 / 03
25 min
Lessons learned
An honest account of a deployment: what worked, what did not and what it cost.
L10 / 04
30 min
Technical deep dive
Architecture, implementation and troubleshooting, in proper detail.
L10 / 05
30 min
Community Q&A
Practical questions, answered by people who have done the work.
How a session comes together
You ask the question.
The community
answers it.
SIP is built from what members send in, whether that is a talk they want to give or a subject they want somebody else to explain.
- 01NominatePut forward a subject you want explained, a talk you could give or a project you would like to demo. A sentence is enough.
- 02Find the right personWhere a request needs a speaker, Layer10 looks for somebody in the community who has actually done it.
- 03Shape the sessionEvery speaker agrees what they will leave people with: an architecture, a lesson, some code or a checklist.
- 04On the dayTalks, demos and Q&A, kept short and practical, then drinks with the speakers still there.
- 05You decide what is nextBefore the drinks, everyone nominates and votes on the subjects for the next SIP.
A typical afternoon
1:00pm to 7:00pm.
Talks first, then drinks.
Sessions finish at 4:35pm. After that it is drinks and conversation until seven, so it works as an afternoon out of the office without an overnight stay.
- 1:00pm30 min
- Arrival, coffee and introductionsInformal networking with attendees, speakers and community members.
- 1:30pm10 min
- Welcome to Layer10:SIPThe community, the no-pitch principle and the subjects members have nominated.
- 1:40pm25 min
- Community story: what actually worked?An enterprise or partner practitioner on a real deployment: the challenges, the failures and the lessons.
- 2:05pm25 min
- Show and tell: under the hoodA live demonstration of a UC, voice, contact centre, AI or CPaaS integration.
- 2:30pm20 min
- Coffee and conversationA chance to carry on the conversations the first half started.
- 2:50pm30 min
- Three ideas, three perspectivesThree ten-minute lightning talks on challenges or ideas the community nominated.
- 3:20pm30 min
- Technical deep diveArchitecture, implementation, troubleshooting or a real-world case study, in detail.
- 3:50pm30 min
- Community Q&A: ask us anythingAn open panel. Bring practical questions and your own experience.
- 4:20pm15 min
- What is next? You decideNominate future subjects, volunteer to present and vote on the next SIP.
- 4:35pm2 hr 25 min
- Networking drinksNo presentations and no scheduled meetings. Drinks, light refreshments and the people behind the technology.
- 7:00pm
- Carriages
Our side of it
What will not
happen to you.
SIP only works if the talks are worth an afternoon out of the office. These are the rules that keep them that way.
The rules for speakers
Nobody buys a slot. No sponsored presentations, no paid speaking and no slot bundled into a package.
Teach, do not sell. Vendors are welcome to speak when they bring genuine technical substance. A pitch is not that.
Leave something usable. Every speaker shares something people can take away: an architecture, a lesson, some code or a checklist.
A practitioner every time. At least one session at every SIP comes from an enterprise practitioner talking about their own work.
Failures are welcome. An honest account of what went wrong is worth more than another reference architecture.
Members choose the subjects. Topics are nominated and voted on by the community, not sold to the highest bidder.
Layer10:SIP_
Less pitching.
More teaching.
More teaching.
Share Ideas & Perspectives.
Put forward a subject you want explained or a talk you could give. Every SIP is built from what members send in.
Dates and cities follow the subjects members nominate. Register your interest and we will tell you when the next one is confirmed.
Ticket
£100per person
Your ticket includes
- The full afternoon of talks and demos
- Community Q&A and the vote on the next SIP
- Networking until 7:00pm
Maximum three tickets per company.
SIP, RTP or ICE?
Three ways to
learn from each other.
SIP is for learning from people who have done it. RTP is for talking it over with peers. ICE is for working a hard industry question through together.
| SIP | RTP | ICE | |
|---|---|---|---|
| Purpose | Share knowledge | Relaxed peer conversation | Explore industry challenges |
| Audience | Open technical community | Enterprise or partner, never combined | Mixed industry |
| Vendors | Welcome if they teach | Not at the table | Welcome as participants |
| Format | Talks, demos and Q&A | Informal dinner round one table | Facilitated exchange |
| Outcome | Learning and practical skills | Peers and shared experience | Industry insight |
Before you register
Questions people
actually ask.
If something is not answered here, ask us before you register.
Do I have to present?
No. Most people come to learn. If you do have something worth showing, put it forward and we will help you shape it.
I want something explained rather than to present. Can I ask?
Yes, and it is one of the most useful things you can do. Nominate the subject and Layer10 will look for somebody in the community who has done it.
Can vendors speak?
Yes, when they bring genuine technical substance: how something works, how it was built, what went wrong. Nobody can buy a slot, and a talk that turns into a pitch is not the kind that gets asked back.
Can sponsors and benefactors come?
One person each. Community Benefactors, Founding Benefactors and the organisations sponsoring that SIP can each send one person to take part, as a participant like everybody else. It does not come with a speaking slot.
How technical is it?
Practical rather than theoretical. Expect architecture diagrams, live demos and real numbers, pitched so that people from neighbouring disciplines can follow.
Can I bring colleagues?
Up to two of them. Tickets are capped at three per company, so the audience is a proper mix of organisations rather than one team and its suppliers.
Do I need to stay for the drinks?
No. The sessions finish at 4:35pm and the networking runs until seven for anyone who wants it.
Is the social part SIPFACED?
No. SIPFACED is the after-party at PACKETLOSS. SIP finishes with relaxed drinks and conversation, not a party.
How is it different from PACKETLOSS?
PACKETLOSS is the flagship: a full conference with an exhibition. SIP is a single afternoon for up to a hundred people, built from subjects the community nominates.
Elsewhere in the series
Enterprise edition
Layer10:SDP_
Share. Discuss. Progress.
A half-day roundtable for enterprise technology users. Four facilitated workshops of fifteen people, on topics the community submits beforehand.
Explore SDP →Informal roundtables
Layer10:RTP_
Real Talk. Real People.
Relaxed roundtable conversations for people working in UC, contact centre and AI. A private table at a venue with something to do, a set menu and up to twenty people who do the same job, in London and Liverpool, with separate groups for enterprise teams and partners.
Explore RTP →
Regional meetups
Layer10:MOS_
Meet. Open. Share.
A free evening meetup for people working across UC, voice, contact centre, AI and CPaaS. Two short talks the community voted for, then drinks and conversation until nine.
Explore MOS →
Annual cross-industry exchange
Layer10:ICE_
Industry Connections Exchange.
Once a year, every March, before budgets and roadmaps are set. One big industry question, broken into solvable parts by enterprise practitioners, partners, vendors and independent specialists, then written up as a report.
Explore ICE →
Channel event
Layer10:SYNC_
Share Your Network & Connect.
The independent day for UC, voice, contact centre, AI and CPaaS partners: community-chosen talks, shared problems worked through together, and a limited number of vendors looking for partners. Once a year, 80 to 100 partners, £100 a ticket.
Explore SYNC →