Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pw44

Pages: 1 2 [3] 4 5 ... 44
31
Users / Re: No VPN Connection on 10.04
« on: November 24, 2012, 04:34:47 pm »
Hi Sambuca,
yes, xl2tpd is running.


/var/log/auth.log
Code: [Select]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [RFC 3947] method set to=109
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike] method set to=110
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring unknown Vendor ID payload [8f8d83826d246b6fc7a8a6a428c11de8]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring unknown Vendor ID payload [439b59f8ba676c4c7737ae22eab8f582]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring unknown Vendor ID payload [4d1e0e136deafa34c4f3ea9f02ec7285]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring unknown Vendor ID payload [80d0bb3def54565ee84645d4c85ce3ee]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring unknown Vendor ID payload [9909b64eed937c6573de52ace952fa6b]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 110
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 110
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] meth=106, but already using method 110
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
Nov 24 13:29:35 dcerouter pluto[21730]: packet from 186.242.129.142:500: received Vendor ID payload [Dead Peer Detection]
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: responding to Main Mode from unknown peer 186.242.129.142
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: STATE_MAIN_R1: sent MR1, expecting MI2
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike (MacOS X): i am NATed
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
Nov 24 13:29:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: STATE_MAIN_R2: sent MR2, expecting MI3
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: ignoring informational payload, type IPSEC_INITIAL_CONTACT msgid=00000000
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: Main mode peer ID is ID_IPV4_ADDR: '186.242.129.142'
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: transition from state STATE_MAIN_R2 to state STATE_MAIN_R3
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: new NAT mapping for #18, was 186.242.129.142:500, now 186.242.129.142:4500
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=aes_256 prf=oakley_sha group=modp1024}
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: the peer proposed: 187.15.164.55/32:17/1701 -> 186.242.129.142/32:17/0
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19: responding to Quick Mode proposal {msgid:0e352bfd}
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19:     us: 192.168.0.160[+S=C]:17/1701
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19:   them: 186.242.129.142[+S=C]:17/51077===?
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19: transition from state STATE_QUICK_R0 to state STATE_QUICK_R1
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19: transition from state STATE_QUICK_R1 to state STATE_QUICK_R2
Nov 24 13:29:36 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #19: STATE_QUICK_R2: IPsec SA established transport mode {ESP=>0x0bfea5b5 <0x46b2c1c7 xfrm=AES_256-HMAC_SHA1 NATOA=none NATD=186.242.129.142:4500 DPD=none}
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: received Delete SA(0x0bfea5b5) payload: deleting IPSEC State #19
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy eroute_connection delete inbound was too long: 100 > 36
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy eroute_connection delete inbound was too long: 100 > 36
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy unk255.10000@192.168.0.160 was too long: 168 > 36
Nov 24 13:29:58 dcerouter pluto[21730]: | raw_eroute result=0
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: received and ignored informational message
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142 #18: received Delete SA payload: deleting ISAKMP State #18
Nov 24 13:29:58 dcerouter pluto[21730]: "L2TP-PSK-NAT"[9] 186.242.129.142: deleting connection "L2TP-PSK-NAT" instance with peer 186.242.129.142 {isakmp=#0/ipsec=#0}
Nov 24 13:29:58 dcerouter pluto[21730]: packet from 186.242.129.142:4500: received and ignored informational message
Nov 24 13:30:01 dcerouter CRON[28937]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 24 13:30:01 dcerouter CRON[28938]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 24 13:30:01 dcerouter CRON[28939]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 24 13:30:03 dcerouter CRON[28939]: pam_unix(cron:session): session closed for user root
Nov 24 13:30:03 dcerouter CRON[28938]: pam_unix(cron:session): session closed for user root
Nov 24 13:30:10 dcerouter CRON[28937]: pam_unix(cron:session): session closed for user root

dcerouter_1031272:/var/log# ps ax | grep xl2
11310 pts/33   S+     0:00 grep --color=auto xl2
23156 ?        Ss     0:00 /usr/sbin/xl2tpd


/var/log/syslog (x2ltpd)
Code: [Select]
Nov 24 13:29:38 dcerouter xl2tpd[23156]: control_finish: Peer requested tunnel 17 twice, ignoring second one.
Nov 24 13:29:43 dcerouter xl2tpd[23156]: last message repeated 2 times
Nov 24 13:29:43 dcerouter xl2tpd[23156]: Maximum retries exceeded for tunnel 40741.  Closing.
Nov 24 13:29:48 dcerouter xl2tpd[23156]: control_finish: Peer requested tunnel 17 twice, ignoring second one.
Nov 24 13:29:48 dcerouter xl2tpd[23156]: Connection 17 closed to 186.242.129.142, port 51077 (Timeout)
Nov 24 13:29:52 dcerouter xl2tpd[23156]: control_finish: Peer requested tunnel 17 twice, ignoring second one.
Nov 24 13:29:53 dcerouter xl2tpd[23156]: Unable to deliver closing message for tunnel 40741. Destroying anyway.
Nov 24 13:29:57 dcerouter xl2tpd[23156]: control_finish: Peer requested tunnel 17 twice, ignoring second one.

Did recheck the configs, but is not working....

32
Users / Re: No VPN Connection on 10.04
« on: November 24, 2012, 01:43:13 am »
News about using l2tp and ipsec?
I get a different result, from outside:
Code: [Select]
Nov 23 22:40:09 dcerouter CRON[5524]: pam_unix(cron:session): session closed for user root
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [RFC 3947] method set to=109
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike] method set to=110
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring unknown Vendor ID payload [8f8d83826d246b6fc7a8a6a428c11de8]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring unknown Vendor ID payload [439b59f8ba676c4c7737ae22eab8f582]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring unknown Vendor ID payload [4d1e0e136deafa34c4f3ea9f02ec7285]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring unknown Vendor ID payload [80d0bb3def54565ee84645d4c85ce3ee]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring unknown Vendor ID payload [9909b64eed937c6573de52ace952fa6b]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 110
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 110
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] meth=106, but already using method 110
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
Nov 23 22:40:12 dcerouter pluto[21730]: packet from 187.124.217.240:500: received Vendor ID payload [Dead Peer Detection]
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: responding to Main Mode from unknown peer 187.124.217.240
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: STATE_MAIN_R1: sent MR1, expecting MI2
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike (MacOS X): i am NATed
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: STATE_MAIN_R2: sent MR2, expecting MI3
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: ignoring informational payload, type IPSEC_INITIAL_CONTACT msgid=00000000
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: Main mode peer ID is ID_IPV4_ADDR: '187.124.217.240'
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: transition from state STATE_MAIN_R2 to state STATE_MAIN_R3
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: new NAT mapping for #5, was 187.124.217.240:500, now 187.124.217.240:4500
Nov 23 22:40:12 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=aes_256 prf=oakley_sha group=modp1024}
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: the peer proposed: 187.15.164.55/32:17/1701 -> 187.124.217.240/32:17/0
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6: responding to Quick Mode proposal {msgid:6aad2eab}
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6:     us: 192.168.0.160[+S=C]:17/1701
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6:   them: 187.124.217.240[+S=C]:17/61362===?
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6: transition from state STATE_QUICK_R0 to state STATE_QUICK_R1
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6: transition from state STATE_QUICK_R1 to state STATE_QUICK_R2
Nov 23 22:40:13 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #6: STATE_QUICK_R2: IPsec SA established transport mode {ESP=>0x06bdda38 <0x0874effc xfrm=AES_256-HMAC_SHA1 NATOA=none NATD=187.124.217.240:4500 DPD=none}
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: received Delete SA(0x06bdda38) payload: deleting IPSEC State #6
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy eroute_connection delete inbound was too long: 100 > 36
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy eroute_connection delete inbound was too long: 100 > 36
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: netlink recvfrom() of response to our XFRM_MSG_DELPOLICY message for policy unk255.10000@192.168.0.160 was too long: 168 > 36
Nov 23 22:40:35 dcerouter pluto[21730]: | raw_eroute result=0
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: received and ignored informational message
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240 #5: received Delete SA payload: deleting ISAKMP State #5
Nov 23 22:40:35 dcerouter pluto[21730]: "L2TP-PSK-NAT"[3] 187.124.217.240: deleting connection "L2TP-PSK-NAT" instance with peer 187.124.217.240 {isakmp=#0/ipsec=#0}
Nov 23 22:40:35 dcerouter pluto[21730]: packet from 187.124.217.240:4500: received and ignored informational message
Nov 23 22:42:01 dcerouter CRON[8123]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 23 22:42:02 dcerouter CRON[8123]: pam_unix(cron:session): session closed for user root
Any hints?

I'm not willing to use ppp....

33
Users / Re: FREE Dial in Number in Los Ageles.
« on: November 20, 2012, 05:58:34 pm »
No, i was looking for a DID in LA for my lmce asterisk. I ended renting one from flynumber (US$ 2.95 / month) and it's already working.
For dial out, i do use voipcheap, and for USA, the calls are free for fixed and mobile numbers.
Thx!

34
Users / FREE Dial in Number in Los Ageles.
« on: November 17, 2012, 03:14:37 pm »
Hi,
does anyone knows about free dial in number (for asterisk) in Los Angeles, or at least a low rate flat dial in number service in Los Angeles?
Thx in advance for any hint or help.
Paulo

35
Users / Re: Solved: Dianemo S: Sony IP Control Remote
« on: November 02, 2012, 02:44:13 am »
Hi,
is there a way to get the sony ip control remote template on the regular linuxmce?
Best regards,
Paulo

36
Users / Re: # Images for a room limited?
« on: October 31, 2012, 06:31:02 pm »
I'll throw you even a bone if i go a feed the animals in the back... :p

I did love it!!!!!!!!!!!!!!!!!!!

37
Users / Re: No VPN Connection on 10.04
« on: October 29, 2012, 11:49:56 pm »
It's all in this wiki: http://wiki.linuxmce.org/index.php/PPTP_server
I created it two years ago.

38
Users / Re: No VPN Connection on 10.04
« on: October 29, 2012, 02:06:46 pm »
Append it to /usr/pluto/bin/Network_Firewall.sh

39
Users / Re: No VPN Connection on 10.04
« on: October 29, 2012, 03:24:46 am »
For ppp, you need to enable the protocol 47, only opening port 1723 will not work.
Insert the following iptables rules:

iptables --append FORWARD -o ppp+ --protocol tcp --tcp-flags SYN,RST SYN --jump TCPMSS --clamp-mss-to-pmtu
iptables --append INPUT  --protocol 47 --jump ACCEPT
iptables --append OUTPUT --protocol 47 --jump ACCEPT

40
Users / Re: FreePbx
« on: October 25, 2012, 09:44:27 pm »
Ja, mein Kommandant! Werde da nachschauen!

41
Users / Re: [SOLVED] Prefix, dialplan in 1004
« on: October 25, 2012, 09:25:52 pm »
Hi,
my current dialplan is:

mysql> select * from extensions where context='outbound-allroutes'
    -> ;
+------+--------------------+-------+----------+-------+---------------------------------------------+
| id   | context            | exten | priority | app   | appdata                                     |
+------+--------------------+-------+----------+-------+---------------------------------------------+
| 5936 | outbound-allroutes | 190   |        1 | Macro | dialout-trunk,/,${EXTEN},,                  |
| 5937 | outbound-allroutes | 190   |        2 | Macro | outisbusy,                                  |
| 5938 | outbound-allroutes | 193   |        1 | Macro | dialout-trunk,/,${EXTEN},,                  |
| 5939 | outbound-allroutes | 193   |        2 | Macro | outisbusy,                                  |
| 5976 | outbound-allroutes | _7.   |        1 | Macro | dialout-trunk,SIP/054138594676,${EXTEN:1},, |
| 5977 | outbound-allroutes | _7.   |        2 | Macro | outisbusy,                                  |
| 5958 | outbound-allroutes | _8.   |        1 | Macro | dialout-trunk,SIP/2122498618,${EXTEN:1},,   |
| 5959 | outbound-allroutes | _8.   |        2 | Macro | outisbusy,                                  |
| 5940 | outbound-allroutes | _9.   |        1 | Macro | dialout-trunk,SIP/2062036594,${EXTEN:1},,   |
| 5941 | outbound-allroutes | _9.   |        2 | Macro | outisbusy,                                  |
+------+--------------------+-------+----------+-------+---------------------------------------------+

The trunks:
1 sipgate (dialout-trunk,SIP/054138594676)
2 spa3102 (dialout-trunk,SIP/2122498618)
3 voipcheap (dialout-trunk,SIP/2062036594)

The plans (by trunk)
1 - sipgate
dial rules:
00+XXXXXXX.
outbound:
900|XXXXXXX.
trunk sequence: voipceap, sipgate


2 - spa3102
dial rules:
XXXXXXXX
08+08|00XXXXX.
005521|XXXXXXXX
031+0055|XXXXXXXXXX
031+0|XXXXXXXXXX
031+XXXXXXXXXX
outbound:
121|XXXXXXXX
19X
1|XXXXXXXXXX
9|0055ZXXXXXXXXX
9|0800XXXXX.
9|0ZXNXXXXXXX
9|NXXXXXXX
9|ZXX
trunk sequence: spa3102

3 - voipcheap
dial rules:
00+XXXXXXX.
outbound:
800|XXXXXXX.
900|XXXXXXX.
trunk sequence: voipcheap, sipgate

Ok, how do i insert it in the table, defining the rules, outbound and trunk order, please?
I want to use the prefix 9 for all. For now, as i'm not finding out how, i defined 3 prefixes (uggly :().....

Best regards,

Paulo


42
Users / Re: FreePbx (SOLVED).
« on: October 25, 2012, 08:34:14 pm »
For the PSTN line setup a phone line in lmce as spa with the phone number (1234567890) as the user and in spa3102 config under pstn line

Line Enable:   yes      
 
SIP Settings
SIP Port:   5061      
 
Proxy and Registration
Proxy:   192.168.80.1
Register:   yes   Make Call Without Reg:   yes
Register Expires:   300   Ans Call Without Reg:   yes
  
Subscriber Information
Display Name:   Unknown  Caller   User ID:   phone number
Password:   password   Use Auth ID:   yes
Auth ID:   phone number   


With those settings the spa3102 pstn line registers for me.

Thank you. It worked. spa3102 registered. This is a difference between the old asterisk (used in release 8.10) and the new one (used in release 10.04).

Again, big THX!!!!!!!!!!!!

Wiki updated with the info.

43
Users / Re: FreePbx
« on: October 25, 2012, 08:13:05 pm »
I'm not blaming not having freepbx, but the lack of documentation and information, and that's not your fault. I know it's a volunteer effort and i also understand it's not easy to make it easy for end users.
I would gladly help, if i had the time and the knowledge for it. Some very little contribution i gave (fail2ban, and some voip trunk settings).  

Well, if i can suggest, how about a little tutorial about, comparing the freepbx settings (trunk - peer detail, user detail), outbound route, dialplan according to trunk and register, or a hidden panel where we could tune it.

For me, at least following directives are missing.
* 83    0    18    0    sip.conf    general    alwaysauthreject    yes
* 85    0    18    0    sip.conf    general    nat                            yes
* 86    0    60    0    sip.conf    general    externhost            mydyndns.homeunix.org
* 87    0    5    0    sip.conf    general    externrefresh            5
* 88    0    60    0    sip.conf    general    localnet                   192.168.80.0/255.255.255.0
* 89    0    9    0    sip.conf    general    allow                    g729
* 90    0    10    0    sip.conf    general    allow                    g723
* 91    0    101    0    sip.conf    general    register                    pwollny:XXXXXXXXX@sip.voipcheap.com/2062036594


I don't know if i did it right, because i could not find what are cat_metric and var_metric for.
I'm not asking to have someone doing it for me, but i wish to know where to put what i need, and i'm not finding out :(

Best regards to all,

Paulo

44
Users / Re: FreePbx
« on: October 25, 2012, 07:57:01 pm »
For the PSTN line setup a phone line in lmce as spa with the phone number (1234567890) as the user and in spa3102 config under pstn line

Line Enable:   yes      
 
SIP Settings
SIP Port:   5061      
 
Proxy and Registration
Proxy:   192.168.80.1
Register:   yes   Make Call Without Reg:   yes
Register Expires:   300   Ans Call Without Reg:   yes
 
Subscriber Information
Display Name:   Unknown  Caller   User ID:   phone number
Password:   password   Use Auth ID:   yes
Auth ID:   phone number   


With those settings the spa3102 pstn line registers for me.

Gbutters,

thank you for your email. I will try this configuration later and will report back with results..

Best regards,

Paulo

45
Users / Re: FreePbx
« on: October 25, 2012, 07:50:56 pm »
Pw44,

Your problem is within the authentication of your PSTN line., but you know that already.

Three things I would look at: (make note of any changes you make)

1: Did you set the spa for dhcp or assign it a dynamic ip? If you have it as dhcp, change it to static and try that then change the #2 next, if it still don't work put it back.


spa is setted to a fixed ip address 192.168.80.30

Quote

2: in the spa under "Proxy and Registration" is it set for yes, if so try to set it to off and then check if it works. If it is set to on it tries to tell LMCE what your spa address is, and since you already assigned an ip you don't need to register.


Proxy and Registration: Register is set to YES. I will give a try with NO.

Quote
3: as much as I hate to say this, go back to LMCE 8.10 because the current 10.04 will not work without the ability to setup this box with something like (here it comes, wait, wait,) FREEPBX...... and don't feel too bad as you won't be the only one having to do it.

I myself was going to try and set LMCE up to be an extension of my asterisk box, but after studying how LMCE communicates with asterisk I can't do that either nor can I make the asterisk box work as a in/out trunk to the LMCE because of the changes they made in how the LMCE deals with asterisk. I'm still not sure if I fully understand why the powers to be had to change up asterisk/lmce. If it truly was an issue (as I have read on some other post) that too many people were breaking LMCE using FreePbx I would have thought it would have been easier to just make FreePBX an add-on and not offered help when they screwed it up, just my opinion.

microbrain


Yes, would be prefereable do have something like freepbx, but it's gone, so learning all again from ground zero (where and what, beside the criptic syntax, which was hidden by freepbx). But, as said, it's gone.

Thx for your trying to help :) Let's see if we get it, mostly by trial and error, due lack of documentation.

Pages: 1 2 [3] 4 5 ... 44