Please use [email protected] for questions on how to develop a SIP implementation. Do not cross-post questions to [email protected].
/a On 3/18/10 9:41 AM, Nitin Kapoor wrote: > Hello, > > I have the scenario where the call is coming to SBC from my source UA > and then I am forwarding the same call to redirect server to route the > call. > > Here is the scenario. > > 1) Call come to my source UA and then I forwarded the call to redirect > server with below REQUEST uri. > > Request-Line: INVITE sip:[email protected] > <mailto:sip%[email protected]>;user=phone SIP/2.0 > Request-URI: sip:[email protected] > <mailto:sip%[email protected]>;user=phone > To: sip:[email protected] > <mailto:sip%[email protected]>;user=phone > From: "Joe Gonzales" <sip:[email protected] > <mailto:sip%[email protected]>;user=phone>;tag=3477742912-272141 > Contact: <sip:[email protected]:5060;user=phone;tgrp=100054CUST> > > 2) Now from here my *redirect server* replied me with below uri in TO > & FROM, but will multiple CONTACT header and on which I have the first > CONTACT user part is with “1” and the others all are same but carry > the “1” with rest of the user part. > > IP/2.0 300 Redirect > To: <sip:[email protected] > <mailto:sip%[email protected]>;user=phone>;tag=a667a4b9fa6bfa35b > From: "Joe Gonzales" <sip:[email protected] > <mailto:sip%[email protected]>;user=phone>;tag=3477742912-272141 > Via: SIP/2.0/UDP > 64.124.207.220:5060;branch=z9hG4bKb96ce5413fe01d59101005f4ae3881c6 > Contact: <sip:[email protected] > <mailto:sip%[email protected]>;dtg=202583VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202393VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202562VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202405VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202163VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202203VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202525VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=201030VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202330VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202206VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202329VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=201906VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=201908VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=201907VEND>, > sip:[email protected] > <mailto:sip%[email protected]>;dtg=201905VEND> > > 3)However after sending the ACK my server again sent the another > invite to my vendor with below REQUEST URI with “1” whereas in first > CONTACT header from redirect was not carrying the “1” Contact: > sip:[email protected] > <mailto:sip%[email protected]>;dtg=202583VEND. > > Request-Line: INVITE sip:[email protected] > <mailto:sip%[email protected]> SIP/2.0 > Request-URI: sip:[email protected] > <mailto:sip%[email protected]> > > Whereby in TO header(of the same INVITE) I do not have the “1” in user > part as below. > > To: sip:[email protected] <mailto:sip%[email protected]> > Contact: sip:64.124.207.220:5060;tgrp=100054CUST > > And because of this my vendor is sending immediate 502 REJECTED. > > Status-Line: SIP/2.0 502 Rejected - Called number is not NATNUM > > Could anyone please help me on this, whether it is a correct or > not,because as far as I know he user part of the Request uri would be > checked first. User part of the Request uri is valid but the To header > is different from Request uri so now a validation for the User part > of the To header will be performed and if the user part is found to be > invalid then a 404 (Not Found) response should sent back. > > Thanks, > Nitin Kapoor > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use [email protected] for questions on how to develop a SIP > implementation. > Use [email protected] for new developments on the application of sip. > Use [email protected] for issues related to maintenance of the core SIP > specifications. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
