While looking into the issues with calls to a Cisco router, I noticed a
few odd 
entries in the router Q931 debug and the ooh323 debug log-

First the router, I see up to three issues-  (This is an outgoing call)
1.  Transfer capability looks like it should be set to speach
2.  The numbertype could/should be set to unkown
3.  I suspect the invalid ie is the callerid, but haven't been able to
suppress it.

Jan 12 18:04:05.036: %CALL_CONTROL-6-NUMBERING_TYPE_NO_MATCH: The called
number
numbering type did not matchThe event for the callid 9011 is being
discarded.

Jan 12 18:04:05.036: ISDN Se1/0:23 Q931: pak_private_number: Invalid
type/plan 0
x0 0x1 may be overriden; sw-type 13
Jan 12 18:04:05.036: ISDN Se1/0:23 Q931: pak_private_number: Invalid
type/plan 0
x0 0x1 may be overriden; sw-type 13
Jan 12 18:04:05.040: ISDN Se1/0:23 Q931: Applying typeplan for sw-type
0xD is 0x
4 0x1, Called num 8063577
Jan 12 18:04:05.040: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8  callref =
0x710F
        Bearer Capability i = 0x8890A2
                Standard = CCITT
                Transer Capability = Unrestricted Digital
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98397
                Exclusive, Channel 23
        Calling Party Number i = 0x00A1, '8001'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0xC1, '8063577'
                Plan:ISDN, Type:Subscriber(local)
Jan 12 18:04:05.088: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8
callref = 0x
F10F
        Cause i = 0x82E404 - Invalid information element contents

On the asterisk server, the incomming call results in this log,
showing a failure to encode the UserInfo element.

10:08:54:227  Received SETUP message (incoming, ooh323c_1)
10:08:54:227  Call has tunneling active (incoming,ooh323c_1)
10:08:54:227  Local endpoint does not support fastStart. Ignoring
fastStart. (incoming, ooh323c_1)
10:08:54:228  Dtmf mode set to H.245(signal) for (incoming, ooh323c_1)
10:08:54:228  Error: UserInfo encoding failed
10:08:54:228  Error:Failed to encode uuie. (incoming, ooh323c_1)
10:08:54:228  Error:Failed to encode H225 message. (incoming, ooh323c_1)
10:08:54:228  Error: Failed to enqueue Alerting message to outbound
queue. (incoming, ooh323c_1)
10:08:54:228  Sent Message - CallProceeding (incoming, ooh323c_1)
10:08:54:675  H.225 Facility message Received (incoming, ooh323c_1)
10:08:54:675  Unhandled Facility reason type received (incoming,
ooh323c_1)
10:09:03:490  H.225 Release Complete message received (incoming,
ooh323c_1)
10:09:03:490  Cleaning Call (incoming, ooh323c_1)-
reason:OO_REASON_REMOTE_CLE

This is odd, as the channel works fine with Call Manager, and if the
incoming call is routed
through Call Manager first, it works fine.

Any thoughts?

Dan


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
ooh323c-devel mailing list
ooh323c-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ooh323c-devel

Reply via email to