[chan-capi-users] unable to set outgoing MSN

[Harald Buchholz]

Hi Chris,

 

for me these lines worked:

 

[globals]

OUTBOUNDTRUNK => Capi/contr1

 

[incoming]

exten => _0X.,1,Set(oMSN=<myMSN>:)

exten => _0X.,n,Dial(${OUTBOUNDTRUNK}/${oMSN}${EXTEN:1})

 

Best Regards
Harald

 

Von: chan-capi-users-bounces at lists.melware.net [mailto:chan-capi-users-bounces at lists.melware.net] Im Auftrag von Christoph J. WALTHER
Gesendet: Mittwoch, 30. Juli 2008 15:31
An: chan-capi users
Betreff: Re: [chan-capi-users] unable to set outgoing MSN

 

Hi 

...a few month after my initial query, I finally found the time to look into this problem again, but could not solve it (still the main MSN and not the one I want to set is used by the carrier network). So here I am again seeking for help.

What I did:

1. In capi.conf:

commented out these two entries (per: http://threebit.net/mail-archive/asterisk-users/msg15333.html)

[general]                                                                       

;nationalprefix=0                                                               
;internationalprefix=00                                                         


2. In extensions.conf:

The CALLERTON variable was set to these values: 1,2,3,4,6,16,32

; ISDN out                                                                      

exten => _0X.,1,SetCallerPres(allowed)                                          
exten => _0X.,n,Set(CALLERTON=8)                                                
exten => _0X.,n,log(NOTICE,CALLERTON= ${CALLERTON})                             
exten => _0X.,n,Set(CALLERID(number)=987654321)                                   
exten => _0X.,n,Dial(CAPI/ISDN1/${EXTEN}/d,30)                                  
exten => _0X.,n,Hangup()                                                        

I am glad for all information which allow to solve this problem (and of course can provide additional debug/config information). And for the moment I have these questions:

- What other values for CALLERTON should I try out?

- Are any other statements needed (or should be omitted) in extensions.conf  and/or does the order of appearance matter?

- Does it matter from which channel (SIP/misdn) the outgoing call is originated? With misdn (which I use to connect DECT handsets) I see TON-like configuration entry which could be signalled along...

Best regards & TIA

             ChrisW



On Mon, Jan 14, 2008 at 2:34 PM, Armin Schindler <armin at melware.de> wrote:

On Tue, 8 Jan 2008, Christoph J. WALTHER wrote:
> On Jan 7, 2008 12:25 PM, Armin Schindler <armin at melware.de> wrote:
>
>>>    exten => _9X.,n,Set(CALLERID(number)=9876543)
>>>    exten => _9X.,n,Dial(CAPI/ISDN1/${EXTEN:1}/bd,30)
>>>    exten => _9X.,n,Dial(CAPI/ISDN1/9876543:${EXTEN:1}/b,30)
>>>    exten => _9X.,n,Dial(CAPI/ISDN1/9876543:${EXTEN:1},30)
>>>
>>> does not work.

...

>>> In all these attempts I see in the capi trace that
>>>
>>> CallingPartyNumber              = <10 83>9876543
>>
>> Hmm, 0x10 as type-of-number looks odd to me. Maybe the switch
>> is rejecting this type.
>>
>
> ok. glad to see that there is something raising suspicion :-) Any
> suggestions on how to trace this further?

I cannot tell where this setting is coming from. The calling channel is
normaly setting it. But you can change that by setting variable
 CALLERTON=
to another value.


Armin

_______________________________________________
Chan-capi-users mailing list
Chan-capi-users at lists.melware.net
http://lists.melware.net/mailman/listinfo/chan-capi-users




-- 
Chris J. WALTHER
Switzerland, 3052 Zollikofen, Waldheimweg 5
+41 31 911 88 28
cjwalther at gmail.com

-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: http://lists.melware.net/pipermail/chan-capi-users/attachments/20080731/19b0e540/attachment-0001.htm