Hi Brandon Apologies if you have provided this but do you have a PCAP of the INVITE / 400 Bad Request rather than the Pastebin of the INVITE
The last time I had this was because of a missing /r/n on the SDP granted it was not with teams but still difficult to track down. Also, what is the MTU Size, have you checked to see if the is causing packet fragmentation and manifesting in a Bad Request. Are there any clues in the Teams - Call Analytics. Regards Lewis -----Original Message----- From: [email protected] <[email protected]> Sent: 29 December 2022 20:17 To: [email protected] Subject: sr-users Digest, Vol 211, Issue 67 Send sr-users mailing list submissions to [email protected] To subscribe or unsubscribe via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) (Brandon Armstead) 2. Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) (Brandon Armstead) ---------------------------------------------------------------------- Message: 1 Date: Thu, 29 Dec 2022 12:15:16 -0800 From: Brandon Armstead <[email protected]> Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) To: Henning Westerholt <[email protected]> Cc: "Kamailio (SER) - Users Mailing List" <[email protected]> Message-ID: <CABAX3EoF+hfruLiV2Nh_g117_q8diaKxVEyp5hMFO=wykbq...@mail.gmail.com> Content-Type: multipart/alternative; boundary="0000000000005692d905f0fd2538" Henning, There was no reply (reason) available in my case. - Brandon On Thu, Dec 29, 2022 at 11:48 AM Henning Westerholt <[email protected]> wrote: > Hello, > > > > as mentioned before, have a look to the 400 reply reason phrase. This > was done quite good from their side, better than many other vendors. > > Usually, Teams is not too bad if you are using a defined > infrastructure that do not introduce too many variables. We are > usually using a B2BUA in our customer projects for that purpose. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt - > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fskal > atan.de%2Fblog%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=QU%2BzOgPdbmRYh51a9PvptIvVjnTZrGxT8z1G7b2RRGQ%3D&reserved=0 > > Kamailio services - > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgila > wa.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7C0% > 7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI > joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PuDqkZ > QCj2IlxvRsLQGoKFv19K3uVE5RBxvcPKPODwQ%3D&reserved=0 > > > > *From:* Brandon Armstead <[email protected]> > *Sent:* Thursday, December 29, 2022 7:52 PM > *To:* Kamailio (SER) - Users Mailing List > <[email protected]> > *Subject:* [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 > BAD > REQUEST) > > > > Alex & Kaufman, > > > > Appreciate the feedback. The pastebin is one example of about > 1000+ iterations literally of changes. So I'm finally reaching out > :). I haven't tested the socket attribute in record-route change, I > will try this now. As for the angle brackets I've tried with and > without, etc (already) to no effect. The SDP unknown media type seems > to be a Poly thing, so I > *want* to rule this out as its not in my other SDP's and still receive > 400 bad request. > > One more iteration here we go... please feel free to let me know if > you have any other thoughts on the matter :). > > > > Thanks! > > > > - Brandon > > > > On Thu, Dec 29, 2022 at 8:08 AM Alex Balashov > <[email protected]> > wrote: > > Yeah, the grammar says that rr-params are just generic-params, in > which case it's not. I didn't see that -- nicely spotted! > > I think that may be the basis of the 400 Bad Request. I'd be shocked > if it weren't. > > The broken clock of "Microsoft SIP" can still be right twice a day. > > > On Dec 29, 2022, at 10:31 AM, Kaufman <[email protected]> wrote: > > > > In your top Record-Route you have: > > > > socket=; > > > > Not sure if that is legal. > > > > Kaufman > > > > -----Original Message----- > > From: Alex Balashov <[email protected]> > > Sent: Thursday, December 29, 2022 9:02 AM > > To: Kamailio (SER) - Users Mailing List > > <[email protected]> > > Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 > > BAD > REQUEST) > > > > Sorry to hear you're having to interoperate with Teams. It's a > > unique > form of sadism I wouldn't wish upon anyone. > > > > A few theories: > > > > 1) Microsoft doesn't like the "bare" Contact header-value here: > > > > Contact: > sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE:5061;transport=tls > > > > Unlike the careted one right above: > > > > P-Asserted-Identity: > > <sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE> > > > > A bare URI absent other header-params is of course completely legal, > > but > I'm really trying to get inside the imaginary world of antisocial > "Microsoft SIP" here. > > > > 2) Could it be that antisocial "Microsoft SIP" sends 400 as a way of > objecting to something in the SDP, e.g. where a non-demented SIP stack > would send "488 Not Acceptable Here" or "415 Unsupported Media Type"? > > > > I know you've said you tried multiple clients to rule that out, but > > I > wonder if the thing it's objecting to hasn't been ruled out that way. > > > > 3) I saw this media line in the SDP: > > > > m=application 41356 <unknown media type> > > > > What's that? > > > > -- Alex > > > >> On Dec 29, 2022, at 9:51 AM, Brandon Armstead <[email protected]> wrote: > >> > >> Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) > >> always > result in a 400 BAD REQUEST. > >> Example invite below: > >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fn > >> am11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%25 > >> 2Fpast&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > >> 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7 > >> C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > >> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sda > >> ta=5v20CvNnmdiHwfWMBX6tgjMlE1i2aKpFgTnuVFfpyl0%3D&reserved=0 > >> ebin.com%2FF1G1Ce59&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf > >> 739 > >> a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C > >> 638 > >> 079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo > >> iV2 > >> luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cbff6B4g > >> Nr8 > >> A9zs89smJ129y8IyNM9%2B3zVkGhlzpa54%3D&reserved=0 > >> I've taken care to make sure numbers are all E.164 format in > From/To/Contact. I've also taken care to make sure that FQDN is used > in Contact and Record-Route header. > >> I've tried many different variations and have followed the SIP > information here: > >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fn > >> am11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%25 > >> 2Flear&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > >> 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7 > >> C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > >> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sda > >> ta=ELk0UD1Pleq%2FG9j1%2BT18tiuFe0yjflimR9ztnW%2F7oPM%3D&reserved=0 > >> n.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols > >> -si > >> p&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9 > >> b0c > >> 9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531 > >> %7C > >> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I > >> k1h > >> aWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GO26A9FOOoS42yMCWPPGo5PkKo > >> 75c > >> kjSJSkjAeYRsU0%3D&reserved=0 I've also tried several different > >> clients (Bria, Polycom CCX 600, Grandstream, etc) to see if maybe > >> it was > something in the SDP or otherwise causing an issue. > >> SIP Transport is TLS, RTP is SRTP > >> I might also add that OPTION pings are active and Direct Routing > Endpoint is active, so this is successful. I also am able to receive > calls FROM teams to my IP phone(s) without issue. It is only when I > try and call INTO teams (INVITE -> Microsoft Teams) that I always > receive a 400 BAD REQUEST to my INVITE. > >> Any help is appreciated, thank you! > >> > >> - Brandon > >> > >> __________________________________________________________ > >> Kamailio - Users Mailing List - Non Commercial Discussions To > >> unsubscribe send an email to [email protected] > >> Important: keep the mailing list in the recipients, do not reply > >> only > to the sender! > >> Edit mailing list options or unsubscribe: > > > > -- > > Alex Balashov | Principal | Evariste Systems LLC > > > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > > Web: > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.e > varistesys.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=hbww6wEEztE85YqxcN92bpMR%2BkiI9%2BE3jF1i6fQpjEk%3D&reserved=0, > > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.c > srpswitch.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7 > Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7 > C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =4E7a5ZxSvttBiMxl1VTtolmTvS4T5VGZHA00CsbPR2c%3D&reserved=0 > > > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to [email protected] > > Important: keep the mailing list in the recipients, do not reply > > only to > the sender! > > Edit mailing list options or unsubscribe: > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > > unsubscribe send an email to [email protected] > > Important: keep the mailing list in the recipients, do not reply > > only to > the sender! > > Edit mailing list options or unsubscribe: > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.e > varistesys.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=hbww6wEEztE85YqxcN92bpMR%2BkiI9%2BE3jF1i6fQpjEk%3D&reserved=0, > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.c > srpswitch.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7 > Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7 > C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =4E7a5ZxSvttBiMxl1VTtolmTvS4T5VGZHA00CsbPR2c%3D&reserved=0 > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe: > > -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 13683 bytes Desc: not available ------------------------------ Message: 2 Date: Thu, 29 Dec 2022 12:16:26 -0800 From: Brandon Armstead <[email protected]> Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) To: "Kamailio (SER) - Users Mailing List" <[email protected]> Message-ID: <CABAX3EoV3Udr7sU8QXdOn9wAm7OHHTJp56BRHeokkfeDJ=u...@mail.gmail.com> Content-Type: multipart/alternative; boundary="00000000000086476e05f0fd2974" Tim, I don't think this matters in this case. It is currently working as-is with the minor adjustment of removing socket= param from the Record-Route header. - Brandon On Thu, Dec 29, 2022 at 11:54 AM Tim Chubb <[email protected]> wrote: > The request domain is wrong should be your Fqdn not a pstnhub domain, > Set $du to the pstnhub url, also make sure you present the matching > tls cert based on the sni of your fqdn > > You would probably have a decent reason appended to the 400 response, > for all its lack of clear documentation the one thing team's does well > is its error responses, if your not getting a reason your generally > failing at the tls handshake stage (and that's usually not explicitly > setting the sni value for tls to use on the way out to teams) its a > tls issue and you need to explicitly set the domain to use for sni in your > config. > > The record-route header is pretty forgiving inside the teams black > box, I regularly append custom key value pairs to it in production > when tracing flows through system, not tried it with a null value > though but in my experience teams don't care. > > ------------------------------ > *From:* Kaufman <[email protected]> > *Sent:* Thursday, December 29, 2022, 4:11 PM > *To:* Kamailio (SER) - Users Mailing List > <[email protected]> > *Subject:* [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 > BAD > REQUEST) > > In your top Record-Route you have: > > socket=; > > Not sure if that is legal. > > Kaufman > > -----Original Message----- > From: Alex Balashov <[email protected]> > Sent: Thursday, December 29, 2022 9:02 AM > To: Kamailio (SER) - Users Mailing List <[email protected]> > Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD > REQUEST) > > Sorry to hear you're having to interoperate with Teams. It's a unique > form of sadism I wouldn't wish upon anyone. > > A few theories: > > 1) Microsoft doesn't like the "bare" Contact header-value here: > > Contact: sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE > :5061;transport=tls > > Unlike the careted one right above: > > P-Asserted-Identity: > <sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE> > > A bare URI absent other header-params is of course completely legal, > but I'm really trying to get inside the imaginary world of antisocial > "Microsoft SIP" here. > > 2) Could it be that antisocial "Microsoft SIP" sends 400 as a way of > objecting to something in the SDP, e.g. where a non-demented SIP stack > would send "488 Not Acceptable Here" or "415 Unsupported Media Type"? > > I know you've said you tried multiple clients to rule that out, but I > wonder if the thing it's objecting to hasn't been ruled out that way. > > 3) I saw this media line in the SDP: > > m=application 41356 <unknown media type> > > What's that? > > -- Alex > > > On Dec 29, 2022, at 9:51 AM, Brandon Armstead <[email protected]> wrote: > > > > Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) > > always > result in a 400 BAD REQUEST. > > Example invite below: > > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna > > m11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F > > past&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c8a2 > > 1444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7C0%7 > > C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ > > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5v2 > > 0CvNnmdiHwfWMBX6tgjMlE1i2aKpFgTnuVFfpyl0%3D&reserved=0 > > ebin.com%2FF1G1Ce59&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf7 > > 39 > > a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C6 > > 38 > > 079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi > > V2 > > luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cbff6B4gN > > r8 > > A9zs89smJ129y8IyNM9%2B3zVkGhlzpa54%3D&reserved=0 > > I've taken care to make sure numbers are all E.164 format in > From/To/Contact. I've also taken care to make sure that FQDN is used > in Contact and Record-Route header. > > I've tried many different variations and have followed the SIP > information here: > > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna > > m11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F > > lear&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c8a2 > > 1444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7C0%7 > > C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ > > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ELk > > 0UD1Pleq%2FG9j1%2BT18tiuFe0yjflimR9ztnW%2F7oPM%3D&reserved=0 > > n.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols- > > si > > p&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9b > > 0c > > 9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531% > > 7C > > Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik > > 1h > > aWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GO26A9FOOoS42yMCWPPGo5PkKo7 > > 5c > > kjSJSkjAeYRsU0%3D&reserved=0 I've also tried several different > > clients (Bria, Polycom CCX 600, Grandstream, etc) to see if maybe it > > was > something in the SDP or otherwise causing an issue. > > SIP Transport is TLS, RTP is SRTP > > I might also add that OPTION pings are active and Direct Routing > Endpoint is active, so this is successful. I also am able to receive > calls FROM teams to my IP phone(s) without issue. It is only when I > try and call INTO teams (INVITE -> Microsoft Teams) that I always > receive a 400 BAD REQUEST to my INVITE. > > Any help is appreciated, thank you! > > > > - Brandon > > > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > > unsubscribe send an email to [email protected] > > Important: keep the mailing list in the recipients, do not reply > > only to > the sender! > > Edit mailing list options or unsubscribe: > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.e > varistesys.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431532799%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=36%2BHgqWMRpe6FOZMluvYRnG%2FuZZ7kdyjZEaqF54M9Ig%3D&reserved=0, > > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.c > srpswitch.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7 > Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7 > C0%7C0%7C638079553431532799%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =aW1tgwYq35huWvFHJ26WGyX5s8uXmCz5mUacbA9X2ho%3D&reserved=0 > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe: > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe: > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe: > -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 10592 bytes Desc: not available ------------------------------ Subject: Digest Footer _______________________________________________ sr-users mailing list -- [email protected] To unsubscribe send an email to [email protected] ------------------------------ End of sr-users Digest, Vol 211, Issue 67 ***************************************** __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
