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

voip-info.org

Navigation
Today's Deals
Recently Visited Pages
Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Last Changes
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.36s
  • Memory usage: 2.19MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 0.78

SIP method ack

SIP implements a three-way handshake.

  • The caller sends an INVITE
  • The callee sends an 200 OK to accept the call
  • The caller sends an ACK to indicate that the handshake is done and a call is going to be setup

If the first INVITE message includes a SDP call description, the 200OK includes the callee's SDP.

Created by oej, Last modification by marvy on Wed 26 of Apr, 2006 [21:04 UTC]

Comments

Comments Filter

but what if

by Hossam Aldebei on Monday 28 of January, 2008 [14:51:23 UTC]
but what if the last Ack sent to "TO" field not to the "Contact" field as in the RFC 3261 ..then the call will not run normaly which is the case i face nowadays ...how can we solve it "from the B side or from the A side"?

but what if

by Hossam Aldebei on Monday 28 of January, 2008 [14:50:17 UTC]
but what if the last Ack sent to "TO" field not to the "Contact" field as in the RFC 3261 ..then the call will not run normaly which is the case i face nowadays ...how can we solve it "from the B side or from the A side"?

Re:

by edokter on Wednesday 04 of January, 2006 [14:51:35 UTC]
Defenitely not! A 200 OK message is only sent when the call has been successfully established.

by tthorner on Friday 02 of December, 2005 [21:06:16 UTC]
Shouldn't this read:

- The caller sends and INVITE
- The callee sends a 200 OK to accept the call
- The caller sends and ACK to acknowledge the 200 OK and setup the call, thus completing the handshake

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