ID Asterisk

Indihome ke briker

apakah modem ini sudah bisa terhubung ke briker?

Walaupun ada SIP account nya, entah kenapa kok ndak bisa langsung bisa register ke regstrar servernya. Untuk bisa terkoneksi registrar server, harus dirouting manual ke salah satu interface modemnya karena ip addr registrar server biasanya menggunakan ip private 10.x.x.x (kalo di Surabaya, registrar server 10.0.0.110, mungkin beda di tempat lain atau sama).

Brarti masih belum bisa ya

Saya sudah bisa ping outboundproxy nya

[root@sip ~]# ping 10.0.0.110
PING 10.0.0.110 (10.0.0.110) 56(84) bytes of data.
64 bytes from 10.0.0.110: icmp_seq=1 ttl=61 time=2.87 ms
64 bytes from 10.0.0.110: icmp_seq=2 ttl=61 time=2.56 ms
64 bytes from 10.0.0.110: icmp_seq=3 ttl=61 time=2.86 ms
64 bytes from 10.0.0.110: icmp_seq=4 ttl=61 time=2.85 ms

sip*CLI> sip show peers
TLKM19/+622XXXXXX 10.0.0.110 N 5060 OK (6 ms)

sip*CLI> sip show registry
Host dnsmgr Username Refresh State Reg.Time
10.0.0.110:5060 N +622XXXXXX 105 Registered Wed, 07 Dec 2016 23:44:02

masalahnya, kalo dipake outgoing masih channel bussy

Output debug

== Everyone is busy/congested at this time (1:0/0/1)
– Executing [s@macro-dialout-trunk:20] NoOp(“SIP/33-00000042”, “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 127”) in new stack
– Executing [s@macro-dialout-trunk:21] Goto(“SIP/33-00000042”, “s-CHANUNAVAIL,1”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
– Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] Set(“SIP/33-00000042”, “RC=127”) in new stack
– Executing [s-CHANUNAVAIL@macro-dialout-trunk:2] Goto(“SIP/33-00000042”, “127,1”) in new stack
– Goto (macro-dialout-trunk,127,1)
– Executing [127@macro-dialout-trunk:1] Goto(“SIP/33-00000042”, “continue,1”) in new stack
– Goto (macro-dialout-trunk,continue,1)
– Executing [continue@macro-dialout-trunk:1] GotoIf(“SIP/33-00000042”, “1?noreport”) in new stack
– Goto (macro-dialout-trunk,continue,3)
– Executing [continue@macro-dialout-trunk:3] NoOp(“SIP/33-00000042”, “TRUNK Dial failed due to CHANUNAVAIL HANGUPCAUSE: 127 - failing through to other trunks”) in new stack

1 Like

munculnya seperti ini kalau di buat panggilan keluarr

[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] pbx.c: Executing [s@macro-dialout-trunk:22] GotoIf(“SIP/90130501-00000004”, “0?customtrunk”) in new stack
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] pbx.c: Executing [s@macro-dialout-trunk:23] Dial(“SIP/90130501-00000004”, “SIP/telkom_1/085730541151,300,Tt”) in new stack
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] netsock2.c: Using SIP RTP TOS bits 184
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] netsock2.c: Using SIP RTP CoS mark 5
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] app_dial.c: Called SIP/telkom_1/085730541151
[2017-01-10 06:01:41] WARNING[1779][C-00000002] chan_sip.c: Received response: “Forbidden” from ‘sip:+623199112120%40telkom.net.id@10.0.0.110;tag=as6b559c20’
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
[2017-01-10 06:01:41] VERBOSE[2593][C-00000002] pbx.c: Executing [s@macro-dialout-trunk:24] NoOp(“SIP/90130501-00000004”, “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 21”) in new stack

sama lahh dengan saya gan

Coba masuk ke console asterisk dengan ngetik: asterisk -vr

lalu ketik: sip show peers

Bisa register ndak itu ke sip nya lelekom?

menindaklanjuti kendala sebelumnya, hasilnya ada perkembangan bagus. ketika melakukan panggilan keluar sudah bisa nymbung ke nomer yg dituju. tetapi ketika di angkat tidak ada respon, sampai di tutupun tidak ada respon.

[2017-01-20 12:12:58] VERBOSE[26426][C-00000015] pbx.c: Executing [s@macro-dialout-trunk:23] Dial(“SIP/90130501-00000022”, “SIP/telkom_1/082334447478,300,Tt”) in new stack
[2017-01-20 12:12:59] VERBOSE[26426][C-00000015] netsock2.c: Using SIP RTP TOS bits 184
[2017-01-20 12:12:59] VERBOSE[26426][C-00000015] netsock2.c: Using SIP RTP CoS mark 5
[2017-01-20 12:12:59] VERBOSE[26426][C-00000015] app_dial.c: Called SIP/telkom_1/082334447478
[2017-01-20 12:13:03] VERBOSE[26426][C-00000015] app_dial.c: SIP/telkom_1-00000023 is making progress passing it to SIP/90130501-00000022

Setelah di tutup baru muncul log seperti ini
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] app_macro.c: Spawn extension (macro-dialout-trunk, s, 23) exited non-zero on ‘SIP/90130501-00000022’ in macro ‘dialout-trunk

[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Spawn extension (from-internal, 99082334447478, 5) exited non-zero on ‘SIP/90130501-00000022’
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Executing [h@from-internal:1] Macro(“SIP/90130501-00000022”, “hangupcall”) in new stack
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Executing [s@macro-hangupcall:1] GotoIf(“SIP/90130501-00000022”, “1?theend”) in new stack
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Executing [s@macro-hangupcall:3] ExecIf(“SIP/90130501-00000022”, “0?Set(CDR(recordingfile)=)”) in new stack
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Executing [s@macro-hangupcall:4] Hangup(“SIP/90130501-00000022”, “”) in new stack
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] app_macro.c: Spawn extension (macro-hangupcall, s, 4) exited non-zero on ‘SIP/90130501-00000022’ in macro ‘hangupcall’
[2017-01-20 12:13:10] VERBOSE[26426][C-00000015] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on ‘SIP/90130501-00000022’

mohon bila ada yg punya saran dan masukan

ijin menyimak dulu gan, karena posisi sekarang punya sy dikasih fxo card & udah dipake produksi

Saya juga sedang set briker ke sip nya indihome.
Sudah bisa ke 10.0.xx.xx. Paki softphone juga sudah ok.

boleh share config trunk nya pak?

Outgoing & incoming bisa mas ?

woh… voyeur sampe sini juga…

maklum om godril, masih amateur ip-pbx ini.
mesti banyak-banyak ‘main’ sama om godril.

pakai softphone sudah ok, bisa call bisa accept

bisa dipasang di briker nya?

maksudnya,
pakai softphone sudah bisa register ke SIP indihome, call dan terima juga sudah bisa.
briker di segmen network yang sama dengan pc softphone

ini konfig trunk nya di-briker mesti gimana,
401 unauthorized

konfignya

host=10.0.0.10
username=+62548xxxxxx@telkom.net.id
secret=xxxxxx
type=peer
qualify=yes

register string
+62548xxxxxx@telkom.net.id:xxxxxx@10.0.0.10/+62548xxxxxx

ngrep

#
U 192.168.10.24:5060 -> 10.0.0.10:5060
REGISTER sip:telkom.net.id SIP/2.0.
Via: SIP/2.0/UDP 192.168.10.24:5060;branch=z9hG4bK018a464d.
Max-Forwards: 70.
From: <sip:+62548xxxxxx@telkom.net.id>;tag=as2e9b2f8a.
To: <sip:+62548xxxxxx@telkom.net.id>.
Call-ID: 026a8b29386e8cb06d02aed61d028ac3@192.168.2.2.
CSeq: 109 REGISTER.
Supported: replaces, timer.
User-Agent: BrikerIPPBX.
Authorization: Digest username="+62548xxxxxx", realm="telkom.net.id", algorithm=MD5, uri="sip:telkom.net.id", nonce="49FDC38E1623E35800000000BC3A422E", response="7fee57258d9909d7b33af1618266055c", qop=auth, cnonce="364ed8ab", nc=00000001.
Expires: 600.
Contact: <sip:+62548xxxxxx@192.168.10.24:5060>.
Content-Length: 0.
.

#
U 10.0.0.10:5060 -> 192.168.10.24:5060
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 192.168.10.24:5060;received=10.21.224.56;branch=z9hG4bK018a464d.
To: <sip:+62548xxxxxx@telkom.net.id>;tag=h7g4Esbg_6b641ff40bd10e1f90c843a9d55d6231.
From: <sip:+62548xxxxxx@telkom.net.id>;tag=as2e9b2f8a.
Call-ID: 026a8b29386e8cb06d02aed61d028ac3@192.168.2.2.
CSeq: 109 REGISTER.
P-Charging-Function-Addresses: ccf="aaa://telkom.net.id:3870;transport=tcp".
P-Charging-Vector: icid-value=telkom.net.id-1491-280652-834282;icid-generated-at=telkom.net.id.
Service-Route: <sip:10.0.0.10:5060;transport=udp;lr>.
WWW-Authenticate: Digest realm="telkom.net.id",nonce="4595CB4F1623E3580000000034B83830",algorithm=MD5,qop="auth".
Content-Length: 0.
.

apa proxy 10.0.0.10 harus disetting terpisah

Horee!

Akhirnya bisa.

host=10.0.0.10
username=+62548xxxxx@telkom.net.id
secret=xxxxxx
type=peer
qualify=yes

register

+62548xxxx@telkom.net.id:xxsecretxx:+62548xxxx@telkom.net.id@10.0.0.10:5060/+62548xxxx

terimakasih semua!

lho… aku belom ngapa2in kok sudah duluan… wkwkwkkwkw…

Istimewa…bsk coba ah

Kang saya udah berhasil tuh untuk outgoing nya tapi di detik ke 30 disconnect internal server error 500 kira2 apa ya yg kliru di konfigurasi saya ?

1 Like