Hey everyone,
I've set it up so that when the invite comes into Kamailio I suspend the transaction (save the transaction info in sht) and use dispatcher to send a request to our NSS server. On the reply from NSS I throw the identity header into a sht and continue the original transaction. Does that seem like the right way to do it?
The next things I need to look at are: * if first NSS server doesn't respond quickly, try the second (change some timeouts and use dispatcher to try the backup) * if both NSS servers aren't working, I still want to resume the original call and let it through. Maybe I can keep track of the failures in a sht and if I have two failures, resume the original invite without the identity header.
Sound like an ok plan? -- Anthony Wittig Mango Voice Developer
---------- Forwarded message ---------- From: Anthony Wittig awittig@mangovoice.com To: sr-users@lists.kamailio.org, david.villasmil.work@gmail.com Cc: Bcc: Date: Tue, 23 Jan 2024 20:39:09 -0700 Subject: [SR-Users] STIR/SHAKEN Thanks!
This is what I've got so far:
- Kamailio invite -> NSS
- NSS 302 -> Kamailio
- Kamailio ack -> NSS
I can see the identity header on the 302 response in my onreply_route. How can I replay the same invite from step #1 with the identity header I get back in step #2? Should I be doing something with a transaction on step #1, maybe start a branch that goes out to NSS and when it comes back resume the transaction (these are all words I've heard smart people say, but I don't fully understand them...).
Any pointers would be greatly appreciated, thanks!
Anthony Wittig Mango Voice Developer
---------- Forwarded message ---------- From: David Villasmil david.villasmil.work@gmail.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.kamailio.org Cc: Bcc: Date: Tue, 23 Jan 2024 14:56:52 +0100 Subject: [SR-Users] Re: STIR/SHAKEN Ditto, i do first approach.
Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337
On Tue, Jan 23, 2024 at 2:38 PM Alex Balashov via sr-users < sr-users@lists.kamailio.org> wrote:
These are all valid approaches, depending on preference. Catching 302s and extracting exactly the desired info might be easier with Kamailio, so I suppose, ceteris paribus, I'd recommend the first one.
Dispatcher is a great approach!
On 23 Jan 2024, at 00:01, Anthony Wittig via sr-users <
sr-users@lists.kamailio.org> wrote:
Hello,
We're attempting to add identities to our invites. I believe we want to
send our invites to the NSS, and it'll reply with a 302'd invite with an identity header. We currently use FreeSWITCH for dialplans and media and Kamailio as our SBC.
Should we be trying for something like: FreeSWITCH -> Kamailio -> NSS
(302) -> Kamailio -> PSTN
or would it make more sense to do: FreeSWITCH -> NSS (302) ->
FreeSWITCH -> Kamailio -> PSTN
Assuming we wanted Kamailio -> NSS, is using dispatcher the right
approach? We currently use it for our two Kamailios and our FreeSWITCHs. We're going to have two NSS servers, one for failover.
Any thoughts would be greatly appreciated, thanks!
-- Anthony Wittig Mango Voice Developer __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only
to the sender!
Edit mailing list options or unsubscribe:
-- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800
-
Anthony Wittig