login | register
Sat 30 of Aug, 2008 [01:14 UTC]

voip-info.org

History

SIP method invite

Created by: oej,Last modification on Mon 02 of Oct, 2006 [12:46 UTC] by matsk
From the SIP RFC 3261:


When a user agent client desires to initiate a session (for example, audio, video, or a game), it formulates an INVITE request. The INVITE request asks a server to establish a session. This request may be forwarded by proxies, eventually arriving at one or more UAS that can potentially accept the invitation. These UASs will frequently need to query the user about whether to accept the invitation. After some time, those UASs can accept the invitation (meaning the session is to be established) by sending a 2xx response.

If the invitation is not accepted, a 3xx, 4xx, 5xx or 6xx response is sent, depending on the reason for the rejection. Before sending a final response, the UAS can also send provisional responses (1xx) to advise the UAC of progress in contacting the called user.



Back to SIP

Comments

Comments Filter
222

333Re: yes, that is all fine and dandy! but...

by , Friday 12 of November, 2004 [06:20:24 UTC]
Yes, this is an educated posting, we have graciously paid Digium to help us with this problem. They are stuck on it too! We are open to anyone with the solution! A small bounty is availible too!
222

333yes, that is all fine and dandy! but...

by , Friday 12 of November, 2004 [06:11:11 UTC]
Under a context configuration (which is required for in =incoming DID calls). The authentication method (for ease of channels establishment and DID identification) must be invite, not options.
Under the taditional
[primus}
blah=blah
blah=blah
ect....
We are blasting them with options, not invites!
there proxie is saying "Hell no!"
under the register => blah....
DID auth is in the incoming packet, but asterisk cannot read it!
Can not find DID by asterisk under an auth... method of register => blah.....




222

333Why CSeq 102

by , Friday 12 of November, 2004 [05:35:22 UTC]
We are presently trying to stabilize a connection to primus telco. We are noticing that when you try and authenticate as a context and that for of authentication request a query or (102 options). Any 3rd grader security personel will tell you that a proxy will "block" queries. How can someone manage CSeq request in asterisk? Whay can we not have more control in authentication?
Yes we can register using register => username:password@primusIP:5060
but this creates a whole new set of headaches with incoming DID calls.
ex. Incoming calls do have the proper DID info in the primus packets (rfc ok), but without some crazy tricks trying to statically plant DID info (still not working) in the registration. Asterisk does not see the incoming DID from Primus!
Definate Asterisk Bug!