| 03:04.39 | *** join/#fredlug GGD (~IceChat7@ip72-196-241-104.dc.dc.cox.net) |
| 07:34.42 | *** part/#fredlug GGD (~IceChat7@ip72-196-241-104.dc.dc.cox.net) |
| 13:21.07 | *** join/#fredlug GGD (~IceChat7@ip72-196-241-104.dc.dc.cox.net) |
| 13:32.17 | *** join/#fredlug plarsen (~plarsen@fedora/plarsen) |
| 18:10.03 | *** part/#fredlug GGD (~IceChat7@ip72-196-241-104.dc.dc.cox.net) |
| 18:59.44 | plarsen | The current temperature in NE Vienna, Vienna, Virginia is 97.2°F (2:55 PM EDT on June 24, 2010). Conditions: Mostly Cloudy. Humidity: 51%. Dew Point: 75.2°F. Pressure: 29.80 in 1009.0 hPa (Steady). Severe Thunderstorm Watch 406 in effect until 8 PM EDT this evening... |
| 18:59.46 | plarsen | Sigh :( |
| 19:00.59 | jsmith | Yeah, pretty darn hot |
| 19:03.19 | jsmith | plarsen: Do you know what version of FreePBX your friend is running? |
| 19:06.16 | jsmith | plarsen: (and which version of Asterisk?) |
| 19:06.22 | plarsen | jsmith, sorry no. I can find out though. |
| 19:06.47 | jsmith | plarsen: Please do... I've got the FreePBX maintainer interested (in a private message) |
| 19:07.45 | plarsen | jsmith, not sure I'll get an immediate answer. Hang on - let me try go expedite it :) |
| 19:07.58 | jsmith | plarsen: No worries... just trying to strike while the iron is hot |
| 19:09.29 | plarsen | Trixbox / FreePBX ... |
| 19:09.32 | plarsen | How can he tell the version? |
| 19:10.31 | plarsen | Downloaded it about 1-2 month ago. |
| 19:10.43 | plarsen | It's a "trix box" - he doesn't know how to tell the version :( |
| 19:10.51 | plarsen | 2.5 - 2.5.2 ? |
| 19:11.02 | plarsen | jsmith, |
| 19:11.05 | jsmith | That sounds right |
| 19:11.12 | plarsen | core is 5.5.2.4 ... not sure what core means here |
| 19:11.48 | jsmith | Yeah, not sure what that is either... 2.5.2 is what I needed |
| 19:12.01 | jsmith | Do you know if it's running Asterisk 1.4.x or 1.6.x.y? |
| 19:12.39 | plarsen | How can he tell, jsmith ? |
| 19:12.50 | plarsen | he doesn't know the command/way to tell |
| 19:12.56 | jsmith | asterisk -rx 'core show version' |
| 19:13.06 | jsmith | from the command-line interface |
| 19:13.11 | jsmith | (as root) |
| 19:13.30 | plarsen | 1.6.0.1.0 |
| 19:14.51 | jsmith | OK... next question... is there a line near the bottom of /etc/asterisk/sip.conf that says #include sip_custom_post.conf? |
| 19:16.08 | jsmith | If so, add the following two lines to sip_custom_post.conf: |
| 19:16.32 | jsmith | [the-name-of-the-sip-device-from-sip.conf](+) |
| 19:16.35 | jsmith | call-limit=99 |
| 19:17.20 | jsmith | You'll need those two lines for each SIP device, unfortunately |
| 19:17.57 | plarsen | he says it's empy |
| 19:18.44 | plarsen | Trying to get him to assertain what the sip device name is ;) |
| 19:19.28 | jsmith | In sip.conf, there should be some sections that look something like: |
| 19:19.30 | jsmith | [bob] |
| 19:19.33 | jsmith | type=friend |
| 19:19.36 | jsmith | secret=donuts |
| 19:19.43 | jsmith | host=dynamic |
| 19:19.46 | jsmith | etc, etc. |
| 19:20.15 | jsmith | In this case, you'd need to add the following to sip_custom_post to get the SIP device state tracking to work for that device |
| 19:20.17 | plarsen | bob = device |
| 19:20.21 | plarsen | ? |
| 19:20.22 | jsmith | [bob](+) |
| 19:20.25 | jsmith | call-limit=99 |
| 19:20.28 | jsmith | Correct! |
| 19:20.34 | plarsen | he says he only sees [general] ? |
| 19:20.53 | jsmith | OK, it may be in one of the other files that starts with sip_ |
| 19:20.56 | jsmith | sip_nat.conf |
| 19:21.02 | jsmith | sip_<something>.conf |
| 19:21.18 | jsmith | I'm not a big FreePBX user, so I don't remember exactly which file those get stuck in |
| 19:21.26 | plarsen | ahh |
| 19:23.09 | plarsen | sip_additional.conf sip_custom.conf sip_general_custom.conf sip_registrations.conf |
| 19:23.09 | plarsen | sip.conf sip_custom_post.conf sip_nat.conf sip_registrations_custom.conf |
| 19:23.09 | plarsen | sip.conf.0 sip_general_additional.conf sip_notify.conf |
| 19:23.13 | plarsen | which one? :) |
| 19:25.25 | plarsen | sip_additional has "call_limit=50" |
| 19:27.16 | plarsen | seems "sip_additional" lists all his extensions so the setting is per extension |
| 19:30.48 | jsmith | Correct |
| 19:31.26 | jsmith | It is per device |
| 19:34.17 | plarsen | How does he reload without killing connections after changing the files? |
| 19:34.28 | jsmith | "sip reload" from the Asterisk CLI |
| 19:34.40 | jsmith | or 'asterisk -rx "sip reload"' from the Linux CLI |
| 19:35.19 | plarsen | It's parsing ... :) |
| 19:37.50 | plarsen | out of curriosity - what does the (+) indicate? |
| 19:38.14 | plarsen | He's testing after changing per extension for a few numbers. Unable to figure out what "device name" to use for now. |
| 19:42.28 | plarsen | thanks for your help; hopefully this will work. Guess if he sends me a dump of the above *.conf files I can make an educated guess of what the device name is ;) |
| 19:45.13 | plarsen | jsmith, He says there's still a problem. The "sip_additional" already contained a call_limit=50 - he changed that to call_limit=99 for 3 extensions. He then had an active call on one, did a intercom call to the busy number, and it put his active call on hold |
| 19:55.55 | jsmith | plarsen: It means "Add these settings to a device previously defined" |
| 21:17.12 | plarsen | This sat is Fredlug day right? |
| 21:17.22 | plarsen | Well, at least Fredlug morning :) |
| 22:05.46 | *** join/#fredlug GGD (~IceChat7@static-66-173-228-42.t1.cavtel.net) |