asterisk users - Aug 2005 - OH323 with Asterisk@home - seems incomplete

I installed oh323 and everything seemed to go smoothly (compile & everything
upto calling through using oh323).

 

I must admit, there is some behavior that's doesn't seem right but
generally, I'm able to dial-out of any oh323 device whether to an extension
or to a trunk. Audio is sometimes muted when dialing out until the extension
or dialed number answers. Sound quality is good when it's there.

 

Following the install, I do not seem to have the option to create an oh323
extension or trunk. Something that I need to do.

 

I realize it's possible to edit the .conf but I needed to ask whether this
was "normal" - doesn't seem like it is to me.

 

Naturally, I'm apprehensive that editing the .conf files manually may be
overwritten by AMP, but even if not, it would seem like it should've been
the norm to have "added" an entry like oh323 to SIP, IAX2 etcetera
types of
trunks. Also, extension types (which work from a drop-down list) should have
been modified.

 

I would appreciate if someone familiar with the application could inform
whether this is "normal" before I attempt to add extensions and trunks
manually.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050823/18089cd5/attachment.htm

Abdel Rahman Tarzi wrote:
>
> Following the install, I do not seem to have the option to create an 
> oh323 extension or trunk. Something that I need to do.
>
> I realize it?s possible to edit the .conf but I needed to ask whether 
> this was ?normal? ? doesn?t seem like it is to me.
>
> Naturally, I?m apprehensive that editing the .conf files manually may 
> be overwritten by AMP, but even if not, it would seem like it 
> should?ve been the norm to have ?added? an entry like oh323 to SIP, 
> IAX2 etcetera types of trunks. Also, extension types (which work from 
> a drop-down list) should have been modified.
>
> I would appreciate if someone familiar with the application could 
> inform whether this is ?normal? before I attempt to add extensions and 
> trunks manually.
>
The next version of AMP (1.10.009) will remove any assumptions from the 
dialplan about the technology being used. In short, the dialplan begins 
to care about devices - and the devices can be any Asterisk supported 
technology. In the AMP interface you can create a Custom Device and 
provide an appropriate dial string.

Feel free to check out 009 (currently in beta) to test your 
configuration on a Development machine. Please note that the 
implementation is subject to change.

Regards,

-- 
Jason Becker
Director & CEO
Coalescent Systems Inc.
Enabling Open Source Telephony
403.244.8089
www.coalescentsystems.ca

Abdel Rahman Tarzi wrote:
> I installed oh323 and everything seemed to go smoothly (compile & 
> everything upto calling through using oh323).
>
> I must admit, there is some behavior that?s doesn?t seem right but 
> generally, I?m able to dial-out of any oh323 device whether to an 
> extension or to a trunk. Audio is sometimes muted when dialing out 
> until the extension or dialed number answers. Sound quality is good 
> when it?s there.
>
> Following the install, I do not seem to have the option to create an 
> oh323 extension or trunk. Something that I need to do.
>
> I realize it?s possible to edit the .conf but I needed to ask whether 
> this was ?normal? ? doesn?t seem like it is to me.
>
> Naturally, I?m apprehensive that editing the .conf files manually may 
> be overwritten by AMP, but even if not, it would seem like it 
> should?ve been the norm to have ?added? an entry like oh323 to SIP, 
> IAX2 etcetera types of trunks. Also, extension types (which work from 
> a drop-down list) should have been modified.
>
> I would appreciate if someone familiar with the application could 
> inform whether this is ?normal? before I attempt to add extensions and 
> trunks manually.
>
>  
>
I apologize for spamming the list... I failed to mention that Custom 
Trunks support exists in the current version of AMP (1.10.008). Here is 
the text from the "Custom Dial String" tooltip:

Define the custom Dial String. Include the token $OUTNUM$ wherever the 
number to dial should go.

examples:

CAPI/XXXXXXXX:b$OUTNUM$,30,r
H323/$OUTNUM$@XX.XX.XX.XX
OH323/$OUTNUM$@XX.XX.XX.XX:XXXX
vpb/1-1/$OUTNUM$

-- 
Jason Becker
Director & CEO
Coalescent Systems Inc.
Enabling Open Source Telephony
403.244.8089
www.coalescentsystems.ca