login | register
Fri 09 of May, 2008 [16:45 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Shoutbox
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
  • Christopher Faust, Wed 07 of May, 2008 [15:28 UTC]: When I try to startx I ge input not supported. Though before installing asterisk I had no video issue to start the GUI
  • Christopher Faust, Wed 07 of May, 2008 [15:26 UTC]: Hi Nick, I got centos 5.1 and asterisk up But now I cannot start startx I have set the depth from 24 to 16 for the video i810 driver for the i845 on my netvista machine but I cannot start GNOME. Please advise
  • Nick Barnes, Wed 07 of May, 2008 [10:01 UTC]: Howard - You'll need to provide a lot more information if you really want help.
  • Nick Barnes, Wed 07 of May, 2008 [10:00 UTC]: Christopher - Search the Wiki and you'll find a page I wrote detailing exactly what you have to do for Asterisk 1.4 + CentOS 5.1.
Server Stats
  • Execution time: 0.19s
  • Memory usage: 2.19MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 0.70

SIP method invite

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
Created by oej, Last modification by Mats Karlsson on Mon 02 of Oct, 2006 [12:46 UTC]

Comments Filter
Edit

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

by Anonymous on 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!
Edit

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

by Anonymous on 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.....




Edit

Why CSeq 102

by Anonymous on 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!

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:

Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver