Problem with Inbound lines

Support forum for the ViciBox ISO Server Install and ISO LiveCD Demo

Moderators: enjay, williamconley, Staydog, mflorell, MJCoate, mcargile, Kumba

Problem with Inbound lines

Postby B.lee2 » Sun Jan 22, 2012 5:43 pm

Ok this is another problem I have, I am trying to set up the inbound line to call extention 201. It seems to register with the Asterisk server allright, but it doesn't seem to reach my extention.

When I turn on agi debug, I get this:


[Jan 22 17:32:17] -- Executing [201@trunkinbound:1] AGI("SIP/future9-0000006b", "agi-DID_route.agi") in new stack
[Jan 22 17:32:17] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jan 22 17:32:17] AGI Tx >> agi_request: agi-DID_route.agi
[Jan 22 17:32:17] AGI Tx >> agi_channel: SIP/future9-0000006b
[Jan 22 17:32:17] AGI Tx >> agi_language: en
[Jan 22 17:32:17] AGI Tx >> agi_type: SIP
[Jan 22 17:32:17] AGI Tx >> agi_uniqueid: 1327271537.107
[Jan 22 17:32:17] AGI Tx >> agi_callerid: 5141234567
[Jan 22 17:32:17] AGI Tx >> agi_calleridname: 5141234567
[Jan 22 17:32:17] AGI Tx >> agi_callingpres: 0
[Jan 22 17:32:17] AGI Tx >> agi_callingani2: 0
[Jan 22 17:32:17] AGI Tx >> agi_callington: 0
[Jan 22 17:32:17] AGI Tx >> agi_callingtns: 0
[Jan 22 17:32:17] AGI Tx >> agi_dnid: 201
[Jan 22 17:32:17] AGI Tx >> agi_rdnis: unknown
[Jan 22 17:32:17] AGI Tx >> agi_context: trunkinbound
[Jan 22 17:32:17] AGI Tx >> agi_extension: 201
[Jan 22 17:32:17] AGI Tx >> agi_priority: 1
[Jan 22 17:32:17] AGI Tx >> agi_enhanced: 0.0
[Jan 22 17:32:17] AGI Tx >> agi_accountcode:
[Jan 22 17:32:17] AGI Tx >>
[Jan 22 17:32:17] AGI Rx << SET CONTEXT default
[Jan 22 17:32:17] AGI Tx >> 200 result=0
[Jan 22 17:32:17] AGI Rx << SET EXTENSION 9998811112
[Jan 22 17:32:17] AGI Tx >> 200 result=0
[Jan 22 17:32:17] AGI Rx << SET PRIORITY 1
[Jan 22 17:32:17] AGI Tx >> 200 result=0
[Jan 22 17:32:17] -- AGI Script agi-DID_route.agi completed, returning 0
[Jan 22 17:32:17] -- Executing [9998811112@default:1] Wait("SIP/future9-0000006b", "2") in new stack
[Jan 22 17:32:19] -- Executing [9998811112@default:2] Answer("SIP/future9-0000006b", "") in new stack
[Jan 22 17:32:19] -- Executing [9998811112@default:3] Playback("SIP/future9-0000006b", "ss-noservice") in new stack
[Jan 22 17:32:19] -- <SIP/future9-0000006b> Playing 'ss-noservice' (language 'en')
[Jan 22 17:32:24] -- Executing [9998811112@default:4] Playback("SIP/future9-0000006b", "vm-goodbye") in new stack
[Jan 22 17:32:24] -- <SIP/future9-0000006b> Playing 'vm-goodbye' (language 'en')
[Jan 22 17:32:25] -- Executing [9998811112@default:5] Hangup("SIP/future9-0000006b", "") in new stack
[Jan 22 17:32:25] == Spawn extension (default, 9998811112, 5) exited non-zero on 'SIP/future9-0000006b'
[Jan 22 17:32:25] -- Executing [h@default:1] DeadAGI("SIP/future9-0000006b", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Jan 22 17:32:25] AGI Tx >> agi_network: yes
[Jan 22 17:32:25] AGI Tx >> agi_network_script: call_log--HVcauses--PRI-----NODEBUG-----16---------------
[Jan 22 17:32:25] AGI Tx >> agi_request: agi://127.0.0.1:4577/call_log--HVcauses ... ----------
[Jan 22 17:32:25] AGI Tx >> agi_channel: SIP/future9-0000006b
[Jan 22 17:32:25] AGI Tx >> agi_language: en
[Jan 22 17:32:25] AGI Tx >> agi_type: SIP
[Jan 22 17:32:25] AGI Tx >> agi_uniqueid: 1327271537.107
[Jan 22 17:32:25] AGI Tx >> agi_callerid: 5141234567
[Jan 22 17:32:25] AGI Tx >> agi_calleridname: 5141234567
[Jan 22 17:32:25] AGI Tx >> agi_callingpres: 0
[Jan 22 17:32:25] AGI Tx >> agi_callingani2: 0
[Jan 22 17:32:25] AGI Tx >> agi_callington: 0
[Jan 22 17:32:25] AGI Tx >> agi_callingtns: 0
[Jan 22 17:32:25] AGI Tx >> agi_dnid: 201
[Jan 22 17:32:25] AGI Tx >> agi_rdnis: unknown
[Jan 22 17:32:25] AGI Tx >> agi_context: default
[Jan 22 17:32:25] AGI Tx >> agi_extension: h
[Jan 22 17:32:25] AGI Tx >> agi_priority: 1
[Jan 22 17:32:25] AGI Tx >> agi_enhanced: 0.0
[Jan 22 17:32:25] AGI Tx >> agi_accountcode:
[Jan 22 17:32:25] AGI Tx >>

While I haven't looked into the perl script, it seems to be passing along the 201 value fine... now what am I missing? Why does it set the extention to 9998811112?
B.lee2
 
Posts: 116
Joined: Mon Dec 19, 2011 1:25 pm

Postby B.lee2 » Sun Jan 22, 2012 5:54 pm

Current dialplan:

exten => _1NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,2,Dial(SIP/${EXTEN}@future9,,tTor)
exten => _1NXXNXXXXXX,3, Hangup
B.lee2
 
Posts: 116
Joined: Mon Dec 19, 2011 1:25 pm

Postby B.lee2 » Sun Jan 22, 2012 5:56 pm

My server is behind a NAT does it change anything at all?
B.lee2
 
Posts: 116
Joined: Mon Dec 19, 2011 1:25 pm

Postby rrb555 » Mon Jan 23, 2012 11:27 am

what is your inbound DID settings?
One server that I am managing | Single Server | ViciBox Redux 6.0 | VERSION: 2.12-549a | BUILD: 160404-0940 | revision 2508| No other hardware
For help you can send me a direct email info@support.com.ph
rrb555
 
Posts: 585
Joined: Tue Feb 08, 2011 4:24 pm
Location: Quezon City, Philippines

Postby B.lee2 » Mon Jan 23, 2012 12:57 pm

Nevermind, I started digging deep while I didn't even take a look at the GUI. It's solved now. :oops:

Thanks for reading my post though.
B.lee2
 
Posts: 116
Joined: Mon Dec 19, 2011 1:25 pm


Return to ViciBox Server Install and Demo

Who is online

Users browsing this forum: No registered users and 83 guests

cron