[Asterisk-Users] problem with * and Howlink CL-100 ip phone
Nick
nick at freya.pelagiris.org
Sat Sep 13 10:40:17 MST 2003
I have gotten a Howlink CL-100 working with chan_h323, but I forget the
exact details. I think I had to disable fast_start & a few other things
on both ends.
Nick
On Fri, Sep 12, 2003 at 10:17:39PM -0700, asterisk at sasami.anime.net wrote:
> I'm trying to use a Howlink CL-100 ip phone with *
>
> It's h323 phone with very limited protocol support. But it's enough that I
> can use it to dial netmeeting client and artisoft pbx just fine.
>
> When I try to dial my * with it using either chan_h323 or oh323, it seems
> to fail on negotiating H245. Maybe this phone doesn't support it?
>
> I've used all different versions of pwlib/openh323 from most recent to
> older ones like 1.4.9 and both chan_h323 and oh323 and have no success.
>
> Here's trace output from chan_h323:
>
> 0:26.010 H323 Listener:80f1b50 transports.cxx(1423) H323TCP Started connection: host=XXX.XXX.XXX.251:1094, if=XXX.XXX.XXX.252:1720, handle=27
> 0:26.011 H225 Answer:40419ae0 transports.cxx(524) H225 Started incoming call thread
> 0:26.011 H225 Answer:40419ae0 transports.cxx(984) H225 Awaiting first PDU
> 0:26.029 H225 Answer:40419ae0 h323pdu.cxx(474) H225 Receiving PDU: setup
> 0:26.029 H225 Answer:40419ae0 transports.cxx(993) H225 Incoming call, first PDU: callReference=32
> 0:26.029 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: SpeexNarrow-5.95k{sw} <1>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: SpeexNarrow-8k{sw} <2>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: SpeexNarrow-11k{sw} <3>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: SpeexNarrow-15k{sw} <4>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: SpeexNarrow-18.2k{sw} <5>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: G.723.1{sw} <6>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: GSM-06.10{sw} <7>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: G.711-uLaw-64k{sw} <8>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1626) H323 Added capability: G.711-ALaw-64k{sw} <9>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: SpeexNarrow-5.95k{sw} <1>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: SpeexNarrow-8k{sw} <2>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: SpeexNarrow-11k{sw} <3>
> 0:26.030 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: SpeexNarrow-15k{sw} <4>
> 0:26.031 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: SpeexNarrow-18.2k{sw} <5>
> 0:26.031 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: G.723.1{sw} <6>
> 0:26.031 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: GSM-06.10{sw} <7>
> 0:26.031 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: G.711-uLaw-64k{sw} <8>
> 0:26.031 H225 Answer:40419ae0 h323caps.cxx(1687) H323 Found capability: G.711-ALaw-64k{sw} <9>
> 0:26.031 H225 Answer:40419ae0 rfc2833.cxx(78) RFC2833 Handler created
> 0:26.031 H225 Answer:40419ae0 h323ep.cxx(1855) H323 Created new connection: ip$XXX.XXX.XXX.251:1094/32
> 0:26.031 H225 Answer:40419ae0 h323.cxx(1619) H225 Handling PDU: Setup callRef=32
> exten b4: ip$XXX.XXX.XXX.252:1720
> -- Executing Wait("H323/ip$XXX.XXX.XXX.251:1094/32", "1") in new stack
> -- Executing Wait("H323/ip$XXX.XXX.XXX.251:1094/32", "1") in new stack
> 0:26.042 H225 Answer:40419ae0 h323.cxx(1879) H225 Set protocol version to 2 and implying H.245 version 3
> 0:26.043 H225 Answer:40419ae0 h323.cxx(2079) H225 Set remote application name: "Sagitta IP-Phone 1.0 181/1234"
> 0:26.043 H225 Answer:40419ae0 h323.cxx(1919) H225 Sending call proceeding PDU
> 0:26.044 H225 Answer:40419ae0 h323pdu.cxx(474) H225 Sending PDU: callProceeding
> 0:26.046 H225 Answer:40419ae0 h323.cxx(1949) H225 Incoming call accepted
> -- Executing Answer("H323/ip$XXX.XXX.XXX.251:1094/32", "") in new stack
> 0:36.040 H225 Answer:40419ae0 transports.cxx(1525) H323TCP Could not connect to XXX.XXX.XXX.251:1095 (local port=0) - Connection timed out(110)
> 0:36.040 H225 Answer:40419ae0 h323.cxx(3057) H225 Connect of H245 failed: Connection timed out
> 0:36.041 H225 Answer:40419ae0 h323ep.cxx(1536) H323 Clearing connection ip$XXX.XXX.XXX.251:1094/32 reason=EndedByTransportFail
> 0:36.041 H225 Answer:40419ae0 h323.cxx(1403) H323 Call end reason for ip$XXX.XXX.XXX.251:1094/32 set to EndedByTransportFail
> 0:36.041 H225 Answer:40419ae0 h323.cxx(1421) H225 Sending release complete PDU: callRef=32
> 0:36.042 H225 Answer:40419ae0 h323pdu.cxx(474) H225 Sending PDU: releaseComplete
> 0:36.042 H225 Answer:40419ae0 transports.cxx(1023) H225 Signal channel stopped on first PDU.
> 0:36.043 H323 Cleaner h323ep.cxx(1594) H323 Cleaning up connections
> 0:36.043 H323 Cleaner h323.cxx(1458) H323 Connection ip$XXX.XXX.XXX.251:1094/32 closing: connectionState=NoConnectionActive
> 0:36.043 H323 Cleaner transports.cxx(966) H323 H323Transport::Close
> 0:36.044 H323 Cleaner transports.cxx(1048) H323 H323Transport::CleanUpOnTermination for H225 Answer:40419ae0
> 0:36.044 H323 Cleaner h323.cxx(1518) H323 Connection ip$XXX.XXX.XXX.251:1094/32 terminated.
> No connection found for ip$XXX.XXX.XXX.251:1094/32
> == Spawn extension (default, s, 2) exited non-zero on 'H323/ip$XXX.XXX.XXX.251:1094/32'
> 0:36.051 H323 Cleaner h323.cxx(1353) H323 Connection ip$XXX.XXX.XXX.251:1094/32 deleted.
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
More information about the asterisk-users
mailing list