[Asterisk-Users] IAXphone -> ip address -> extension number.

[Zoltan Szecsei]

Rich Adamson wrote:

>>>>>If you don't mind, can you explain me a little more the ztcfg problem. My
>>>>>experience with that is null, but I need to setup a box for testing purposes
>>>>>only, and I don't want to but a TDM card only for make it work.
>>>>>
>>>>>I know people that has asterisk running on SIP that don't use zaptel &
>>>>>Zapata just they do sip also to their provider (which is not my my case) but
>>>>>I never did that.
>>>>>
>>>>>So I plan to install it with Ztdummy on top of FC2.
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>FWIW, I've been running asterisk on a RHv9 laptop (for client demo 
>>>purposes), connecting it via iax to our office system, and never
>>>worried about ztdummy, etc. Obviously, the laptop has no zap cards.
>>>This demo never includes meetme, etc.
>>>
>>> 
>>>
>>>      
>>>
>>I'm not actually surprised. In the Makefile you'll see somewhere around 
>>line 61 that ztdummy is commented out and, if you *want* ztdummy, you 
>>should remove the "#" before running make linux26.
>>However, if you follow through the use of the variable names, you will 
>>see that ztdummy is suffiex anyway so whether you comment it in or out, 
>>ztdummy gets compiled.
>>It would me interesting to do an "lsmod | grep z" on your laptop to see 
>>if zaptel & ztdummy are loaded.
>>
>>
>>    
>>
>>>I also have a backup system (to our office system) running RHv9, and
>>>it connects and functions just fine to the primary office system
>>>via iax. Sip phones work fine on this backup system as well.
>>>
>>>That backup system was just recently replaced with an FC3 system, and
>>>I have no doubt whatsoever it will function just fine without zap
>>>cards although that system has not yet been configured or tested.
>>>
>>>So, don't be too concerned with making ztdummy (etc) function unless
>>>you truly want to support those asterisk apps that need it (eg, meetme
>>>and whatever else the wiki points out).
>>>
>>> 
>>>
>>>      
>>>
>>(I seem to remember IAX needed timing, which is why I was on the ztdummy 
>>mission - no cards in my testbox either.)
>>    
>>
>
>Okay, just fired up the laptop and it registered with our office
>system just fine using iax2. 
>
>The laptop is RHv9 with cvs-head from 4/25/05 with no modifications of
>any sort. The lsmod lists zaptel only, Used = 0, and no ztdummy listed.
>
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>  
>
Hmmm - interesting.
I did an rmmod on both ztdummy and zaptel and then fired up asterisk.
I could still make a call from 1 extension to another, but both 
music_on_hold *and* IAX2 complained about timing (but I could still make 
the call!!). I haven't played with MOH yet, so I dont know if the sound 
will work or be choppy.

Let the mystery remain....?

Cheers,
Zoltan.
***********************************
 [res_musiconhold.so] => (Music On Hold Resource)
  == Parsing '/etc/asterisk/musiconhold.conf': Found
Jul 10 19:20:53 WARNING[3548]: res_musiconhold.c:565 moh_register: 
Unable to open pseudo channel for timing...  Sound may be choppy.
  == Registered application 'MusicOnHold'
  == Registered application 'WaitMusicOnHold'
  == Registered application 'SetMusicOnHold'

*** cut a bit out ******

 [chan_iax2.so] => (Inter Asterisk eXchange (Ver 2))
Jul 10 19:20:53 WARNING[3548]: chan_iax2.c:7477 load_module: Unable to 
open IAX timing interface: No such file or directory
  == Manager registered action IAXpeers
  == Parsing '/etc/asterisk/iax.conf': Found
    -- Seeding 'z1' at 192.168.0.201:4569 for 60
    -- Seeding 'z2' at 192.168.0.202:4569 for 60
  == Registered channel type 'IAX2' (Inter Asterisk eXchange Driver (Ver 2))
  == Using TOS bits 0
  == IAX Ready and Listening on 0.0.0.0 port 4569
  == Loaded firmware 'iaxy.bin'
  == Parsing '/etc/asterisk/iaxprov.conf': Found
    -- Loaded provisioning template 'default'
*******************************************