search for: 91nxxnxxxxxx

I am switching from IAX2 to SIP for my inter-Asterisk transport due to assorted quality issues following the 1.2.4 upgrade. On the server that SENDS the call, I have the following in SIP.CONF: [192.168.1.2_OB] type=peer fromuser=OB host=192.168.1.2 And in EXTENSIONS.CONF exten => 91NXXNXXXXXX,1,Dial(SIP/${EXTEN}@192.168.1.2_OB) On the RECEIVING Server in SIP.CONF: [OB] type=user context=longdistance I am not using a REGISTER statement on the receiving server. My problem is that the only way I can seem to get the call delivered into the proper SIP context on the receiving box is to...

...-canonical include => dundi-dundi-test-customers include => dundi-dundi-test-via-pstn [dundi-dundi-test-switch] switch => DUNDi/dundi-test [dundi-dundi-test-lookup] include => dundi-dundi-test-local include => dundi-dundi-test-switch [macro-dundi-dundi-test] ; Usage: exten => _*91NXXNXXXXXX,1,Macro(dundi-dundi-test,${EXTEN:2}) ; This would lookup the number using DUNDi. exten => s,1,Playback(channel-insecure-warn) exten => s,2,Goto(${ARG1},1) include => dundi-dundi-test-lookup

Hello, Just confirmed this on my end, because of the massive changes that have been made to callerID handling in asterisk 1.0.5 many of the features of the astGUIclient suite will not work on this new version. The latest stable version recommended is Asterisk 1.0.3. We will work on trying to find ways around the new callerID rules that the asterisk developers have put in place and hope to have