During debugging of H323 trunk side (using Jeremy Macnamara's H323
driver in ~/channels/h323) a couple of things come don't quite work
as advertised...
1/ the following line in extensions.conf explicitly sets the
outgoing caller ID (required in my case for downstream GK
processing..)
exten => _1NX.,1,SetCallerID,6400047602100
exten => _1NX.,2,Dial,H323/${EXTEN:1}
what comes out in the h323 datastream and logs is:-
dialled digits
{
{src digits}
{ "6400047602100)" }
.......
note the unbalanced closing backet. We tried changing the
number length, and doing called ID with different functions,
but it looks like a bug.
A fairly detailed squiz around the digium site did not point
where to file a bug to, so I apologise for polluting this list..
================================================================
When the h323 channel driver registers......
vipe50#sho gatek endp
GATEKEEPER ENDPOINT REGISTRATION
===============================CallSignalAddr Port
RASSignalAddr Port Zone Name Type Flags
--------------- ----- --------------- ----- --------- ---- -----
202.37.19.10 1720 202.37.19.10 1024 zone1 TERM
E164-ID: 6400047602201
202.37.19.11 1720 202.37.19.11 1719 zone1 TERM
E164-ID: 6400047602999
;
; Asterisk, strongly preferred as a VOIP-GW, but registers as a TERM.
;
202.37.19.12 1720 202.37.19.12 32829 zone1 TERM
H323-ID: fxchange
E164-ID: 6400047602100
;
; Cisco Call Manager, registering as a VOIP GW, with H323 Trunk
;
202.37.83.10 1720 202.37.83.10 1710 zone1 VOIP-GW
H323-ID: 202.37.83.10
203.79.85.252 1720 203.79.85.252 1719 zone1 TERM
E164-ID: 6400047601020
I had a look through the source, no comments stood out, any know a way
to get * registered as a VOIP-GW, rather than a TERM? Played with all
the obvious things in h323.conf
Many Thanks for reading this far...
Rgds Roger De Salis
--
\_ Roger De Salis rdesalis at fx dot net dot nz
</' FX Networks +64 21 481 452
/) Wellington, New Zealand roger at desalis dot gen dot nz
(/
` Bentley win Le Mans! - What next, English win cricket in Aus?
H.323 doesn't have an explicit caller*id feature, so any callerid specific features that have been added are hacks. Since you are using a gatekeeper why don't you use a type=h323 to specify your H.323 id properly? [6400047602100] type=h323 secret=securepassword ; optional Find me on IRC (JerJer) if u want to discuss this. Jeremy McNamara Roger De Salis wrote:> > During debugging of H323 trunk side (using Jeremy Macnamara's H323 > driver in ~/channels/h323) a couple of things come don't quite work > as advertised... > > 1/ the following line in extensions.conf explicitly sets the > outgoing caller ID (required in my case for downstream GK > processing..) > > exten => _1NX.,1,SetCallerID,6400047602100 > exten => _1NX.,2,Dial,H323/${EXTEN:1} > > what comes out in the h323 datastream and logs is:- > > dialled digits > { > {src digits} > { "6400047602100)" } > ....... > > note the unbalanced closing backet. We tried changing the > number length, and doing called ID with different functions, > but it looks like a bug. > > A fairly detailed squiz around the digium site did not point > where to file a bug to, so I apologise for polluting this list.. > > ================================================================> > When the h323 channel driver registers...... > > vipe50#sho gatek endp > GATEKEEPER ENDPOINT REGISTRATION > ===============================> CallSignalAddr Port RASSignalAddr Port Zone Name Type > Flags > --------------- ----- --------------- ----- --------- ---- > ----- > 202.37.19.10 1720 202.37.19.10 1024 zone1 TERM > E164-ID: 6400047602201 > 202.37.19.11 1720 202.37.19.11 1719 zone1 TERM > E164-ID: 6400047602999 > ; > ; Asterisk, strongly preferred as a VOIP-GW, but registers as a TERM. > ; > 202.37.19.12 1720 202.37.19.12 32829 zone1 TERM > H323-ID: fxchange > E164-ID: 6400047602100 > ; > ; Cisco Call Manager, registering as a VOIP GW, with H323 Trunk > ; > 202.37.83.10 1720 202.37.83.10 1710 zone1 VOIP-GW > H323-ID: 202.37.83.10 > 203.79.85.252 1720 203.79.85.252 1719 zone1 TERM > E164-ID: 6400047601020 > > I had a look through the source, no comments stood out, any know a way > to get * registered as a VOIP-GW, rather than a TERM? Played with all > the obvious things in h323.conf > > Many Thanks for reading this far... > > Rgds Roger De Salis