| 00:00.56 | lancey | this is from some docs about Asterisk AGI |
| 00:02.05 | lancey | but Asterisk doesn't behave like that... |
| 00:02.05 | km- | nice |
| 00:02.05 | km- | 2 out of 2 hunks failed on the patch |
| 00:02.05 | km- | heh |
| 00:02.19 | kram | okies |
| 00:03.18 | km- | I'll apply the patch manuall |
| 00:03.18 | andrewg | 0/win 22 |
| 00:05.15 | km- | that's curious |
| 00:05.15 | km- | why'd the patch fail |
| 00:05.15 | km- | it was totally obvious |
| 00:05.18 | Supaplex | hey boys and girls, wassup? |
| 00:05.18 | kram | did you read the directions? |
| 00:05.18 | kram | and install the pppoe patch first? |
| 00:05.18 | kram | oh wait |
| 00:05.18 | kram | there are no directions |
| 00:05.18 | kram | (doh!) |
| 00:07.08 | km- | hahahahhhaahha |
| 00:07.09 | km- | so you have to put the pppoe patch in there huh |
| 00:07.09 | km- | lemme grab that too |
| 00:07.55 | paulc | lancey: delayed reply.. how does Asterisk behave then? |
| 00:07.55 | km- | I was wondering why zaptel.c was crashing and burning |
| 00:07.55 | *** join/#asterisk dspdavel (~davel@wiggum.digitalcoven.com) [NETSPLIT VICTIM] |
| 00:08.05 | kram | anyway |
| 00:08.08 | kram | install the PPPOE patch first |
| 00:08.08 | kram | maybe you can put a README toegehter when you're done |
| 00:08.08 | kram | deal? |
| 00:08.08 | km- | ahhhhhhh |
| 00:08.08 | km- | I love it when a good thing comes together |
| 00:09.51 | km- | kram: I'm not supposing you've got directions and/or an example options file, do ya?\ |
| 00:09.51 | km- | sure |
| 00:09.51 | km- | I'll document the steps |
| 00:10.37 | km- | okie doke |
| 00:10.41 | km- | I've got 9 steps documented sofar |
| 00:10.56 | km- | I've got the pppd all compiled up with pppoe and zaptel plugin |
| 00:12.36 | km- | my guess is the next step is to configure some sort of options file for pppd to use |
| 00:12.37 | km- | kram: does this method require the kernel hdlc support? |
| 00:12.37 | km- | kram: or is this a pure zaptel implementation? |
| 00:13.59 | km- | Jun 20 20:47:45 sspbx1 pppd[2799]: pppd 2.4.1b2 started by root, uid 0 |
| 00:13.59 | km- | Jun 20 20:47:45 sspbx1 pppd[2799]: tcgetattr: Inappropriate ioctl for device(25) |
| 00:13.59 | km- | Jun 20 20:47:46 sspbx1 pppd[2799]: Exit. |
| 00:14.03 | km- | when I do 'pppd /dev/zap/17 noauth' |
| 00:14.05 | *** join/#asterisk mvn (~mvn@c-66-229-172-124.we.client2.attbi.com) |
| 00:15.03 | km- | heh, it's Inappropriate! :P |
| 00:16.42 | *** join/#asterisk dant (~dan@2001:618:480:0:204:76ff:fe1e:585e) [NETSPLIT VICTIM] |
| 00:16.42 | *** join/#asterisk Marlow (~marlow@loke.home.marlow.dk) [NETSPLIT VICTIM] |
| 00:16.42 | kram | it does not require kernel hdlc |
| 00:16.42 | kram | just kernel pppp |
| 00:16.43 | km- | yep |
| 00:16.43 | km- | got that compiled in, thankfully |
| 00:16.43 | km- | I've gotten so far as to do 'pppd /dev/zap/17 noauth plugin zaptel.so' but I get an inappropriate ioctl on device |
| 00:16.43 | km- | which leads me to believe that I shouldnt be using /dev/zap/17 |
| 00:17.08 | km- | although if I cat /dev/zap/17 I definitely see stuff |
| 00:17.27 | *** join/#asterisk Jestre (~ack@moya.trilug.org) |
| 00:17.28 | kram | you have to use the module |
| 00:17.28 | kram | module zaptel.so |
| 00:17.32 | km- | yes |
| 00:18.00 | kram | pppd plugin zaptel.so stdin < /dev/zap/1 for example |
| 00:19.03 | km- | uhm |
| 00:19.26 | km- | I just did "ppp plugin zaptel.so 17 noauth |
| 00:19.31 | km- | and I think the kernel panicked |
| 00:20.02 | km- | because now the box isn't responding to pings or ssh packets |
| 00:21.01 | kram | hrm |
| 00:21.01 | kram | okay well not sure then |
| 00:21.01 | km- | heheehhehe |