Cisco ATA 186 e.164 address requirement h.323
Last response: in Networking
Archived from groups: comp.dcom.voice-over-ip (More info?)
Does anyone know of a way to work around the fact that the cisco ata
products require an e.164 address in the call setup?
I an trying to use one with an h.323 gatekeeper that does not send the
e.164 address when setting up the call. obviously running h.323 image
on the ata.
I realize that this functionality is required to access the two ports,
but I am just trying to use it as a single port device, and I can not
modify the functionality of the gatekeeper.
The current results are that the ata can place calls via tha
gatekeeper, but ignores all call set up requests from the gatekeeper
for incoming calls becasue of the lack of an e.164 address in the call
setup message.
Does anyone know of a way to work around the fact that the cisco ata
products require an e.164 address in the call setup?
I an trying to use one with an h.323 gatekeeper that does not send the
e.164 address when setting up the call. obviously running h.323 image
on the ata.
I realize that this functionality is required to access the two ports,
but I am just trying to use it as a single port device, and I can not
modify the functionality of the gatekeeper.
The current results are that the ata can place calls via tha
gatekeeper, but ignores all call set up requests from the gatekeeper
for incoming calls becasue of the lack of an e.164 address in the call
setup message.
More about : cisco ata 186 164 address requirement 323
Archived from groups: comp.dcom.voice-over-ip (More info?)
Damon wrote:
> Does anyone know of a way to work around the fact that the cisco ata
> products require an e.164 address in the call setup?
AFAIR this functionality (accept any alias as port1-assigned) is not
possible for ATA.
To avoid such kind of problems i forced my SmartGate softswitch to
replace called alias in outgoing Setup with port-attached for every call
routed to ATA. If your gatekeeper supports number translations at all,
it SHALL to be able to do this. As i can route calls for per-port
basics, i can do this for both ports in independent manner. But if you
use ATA as single port, you don't need this.
--
WBR,
Roman Nikitchenko, http://smartgate.wtelecom.net
_,,,_|\_/|_,,,_
Damon wrote:
> Does anyone know of a way to work around the fact that the cisco ata
> products require an e.164 address in the call setup?
AFAIR this functionality (accept any alias as port1-assigned) is not
possible for ATA.
To avoid such kind of problems i forced my SmartGate softswitch to
replace called alias in outgoing Setup with port-attached for every call
routed to ATA. If your gatekeeper supports number translations at all,
it SHALL to be able to do this. As i can route calls for per-port
basics, i can do this for both ports in independent manner. But if you
use ATA as single port, you don't need this.
--
WBR,
Roman Nikitchenko, http://smartgate.wtelecom.net
_,,,_|\_/|_,,,_
Related ressources:
- ForumConfigure ATA 186 for use with ALTIGEN system
- ForumMGCP and SIP
- Forum2 Sipgate numbers behind one router..?
- ForumRouter Setup
- ForumGSM Box + Cisco VoIP
- ForumLinksys with Cisco ATA186
- ForumQuintum and Cisco Gatekeeper
- ForumAdding/Changing Ringtones on a Cisco 7905G/7912G with SIP ..
- Forumin-band DTMF signalling on Cisco Call Manager 3.3
- ForumH.323: How to register GW without prefix?
- ForumCisco SIP FW?
- ForumFujitsu FDX-840 information wanted (vs the Cisco ATA 186)
- ForumUse different lines on Cisco 7960 in directory and dialplan
- More resources
Read discussions in other Networking categories
!
