Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: rrkelly on February 01, 2011, 12:42:09 AM
-
i have to route calls from a pri (TDM) to a remote sail pbx. on the sail with the pri i can see the caller id and i'm using that as a PTT_DiD_Group with the Open Inbound Route set to an unprivileged sibling trunk to the other sail box that seems to be working.
call comes in on the pri and is routed to the remote sail box. on the remote sail box i have another PTT_DiD_Group with an aliases
set for a ring group . the remote sail also has an unprivileged sibling trunk back to the box with the pri.
if watch on the cli i can see the pri clid accepted an routed to the remote sail i can see it accepted at the remote ip
but instead of hitting the aliases ring group it plays a message that say's you must dial a 1 when dialing this number
below is the cli
-- Executing [5072268302@default:1] AGI("Zap/1-1", "selintra|OutRoute|al800") in new stack
-- Accepting call from '' to '5072268302' on channel 0/1, span 1
-- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
-- AGI Script Executing Application: (NoOp) Options: (test-group)
-- AGI Script Executing Application: (Dial) Options: (IAX2/imtruckrcservicegw~alberleagw@alberleagw~imtruckrcservicegw/5072268302)
-- Called imtruckrcservicegw~alberleagw@alberleagw~imtruckrcservicegw/5072268302
-- Call accepted by 71.87.22.20 (format gsm)
-- Format for call is gsm
-- IAX2/alberleagw~imtruckrcservicegw-16390 is making progress passing it to Zap/1-1
-- IAX2/alberleagw~imtruckrcservicegw-16390 answered Zap/1-1
-- Channel 0/1, span 1 got hangup request, cause 16
-- Hungup 'IAX2/alberleagw~imtruckrcservicegw-16390'
== Spawn extension (default, 5072268302, 1) exited non-zero on 'Zap/1-1'
-- Executing [h@default:1] Hangup("Zap/1-1", "") in new stack
== Spawn extension (default, h, 1) exited non-zero on 'Zap/1-1'
-- Hungup 'Zap/1-1'
-
ok on the remote pbx it is going to the dial app -- i assume i have the remote pbx misconfigurated
i have a PTT_DiD_Group configured with 1 member and it is set to 6001 group but it is hitting the dial script
any idea's
cli below
-- Accepting AUTHENTICATED call from 71.87.22.18:
> requested format = ulaw,
> requested prefs = (ulaw|gsm|alaw),
> actual format = gsm,
> host prefs = (gsm|ulaw|alaw),
> priority = mine
-- Executing [5072268302@internal:1] AGI("IAX2/imtruckrcservicegw~alberleagw-12733", "selintra|OutCluster|5072268302") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
-- AGI Script selintra completed, returning 0
-- Executing [5072268302@default:1] AGI("IAX2/imtruckrcservicegw~alberleagw-12733", "selintra|OutRoute|gsout") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
-- AGI Script Executing Application: (Dial) Options: (SIP/5072268302@MVP810)
-- Called 5072268302@MVP810
-- SIP/MVP810-08af9658 is making progress passing it to IAX2/imtruckrcservicegw~alberleagw-12733
-- SIP/MVP810-08af9658 answered IAX2/imtruckrcservicegw~alberleagw-12733
== Spawn extension (default, 5072268302, 1) exited non-zero on 'IAX2/imtruckrc
-
Hi there
I'm pretty sure it is a little bug in the sip.conf fragment generator. It is causing your call to be processed as privileged (i.e. through the internal context).
-- Accepting AUTHENTICATED call from 71.87.22.18:
> requested format = ulaw,
> requested prefs = (ulaw|gsm|alaw),
> actual format = gsm,
> host prefs = (gsm|ulaw|alaw),
> priority = mine
-- Executing [5072268302@internal:1] AGI("IAX2/imtruckrcservicegw~alberleagw-12733", "selintra|OutCluster|5072268302") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
-- AGI Script selintra completed, returning 0
The important bit is
Executing [5072268302@internal:1]...
It's easily fixed I think. edit this trunk...
imtruckrcservicegw~alberleagw
and set the context to mainmenu (context=mainmenu) instead of internal in the user stanza. It will end up looking something like this...
...
type=user
secret=mysecret
context=mainmenu
...
This should drive the call into the unprivileged (mainmenu) context and process your open/closed rules correctly.
Kind Regards
S
-
ok changed context to mainmenu still does not work -- the call will route to the remote but the remote will not except it in the main menu context -- what contexts are available? we are not using the ivr also when i check the unprivileged siblings neither one local or remote appear up (Peer alberleagw not found. Peer imtruckrcservicegw not found.) is this normal?
remote cli
[Feb 1 07:29:12] NOTICE[5444]: chan_iax2.c:7997 socket_process: Rejected connect attempt from 71.87.22.18, request '5072268302@mainmenu' does not exist
alberleagw*CLI>
thanks
rob
-
ok verified the did is in main menu context in the extendtions.conf file
and the sibling trunks are there
exten => 1005,1,agi(selintra,Inbound,${EXTEN})
exten => 1006,1,agi(selintra,Inbound,${EXTEN})
exten => 1007,1,agi(selintra,Inbound,${EXTEN})
exten => 1008,1,agi(selintra,Inbound,${EXTEN})
exten => 5072668302,1,agi(selintra,Inbound,${EXTEN})
exten => MVP810,1,agi(selintra,Inbound,${EXTEN})
exten => imtruckrcservicegwalberleagw,1,agi(selintra,Inbound,${EXTEN})
exten => imtruckrcservicegw~alberleagw,1,agi(selintra,Inbound,${EXTEN})
exten => intouchgwalberleagw,1,agi(selintra,Inbound,${EXTEN})
exten => masoncitygwalberleagw,1,agi(selintra,Inbound,${EXTEN})
-
I think maybe you have a problem with one of your 6's
exten => 5072668302,1,agi(selintra,Inbound,${EXTEN})
[Feb 1 07:29:12] NOTICE[5444]: chan_iax2.c:7997 socket_process: Rejected connect attempt from 71.87.22.18, request '5072268302@mainmenu' does not exist
alberleagw*CLI>
Kind Regards
S
-
sorry about that --- the extra 6 was the problem -- been looking at it to long
thanks again
rob