René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Erroneous handleDialEvent warning when originating channels","articleBody":"I see a lot of the following warning log due to using channel origination as part of our normal call flow\n\n`handleDialEvent: Ignored DialEvent for unknown source channel null with unique id null`\n\nThis stems from this piece of code in ChannelManager.java\n\n\n```\nvoid handleDialEvent(DialEvent event) {\n        final AsteriskChannelImpl sourceChannel = getChannelImplById(event.getUniqueId());\n        final AsteriskChannelImpl destinationChannel = getChannelImplById(event.getDestUniqueId());\n\n        if (sourceChannel == null) {\n            logger.warn(\"handleDialEvent: Ignored DialEvent for unknown source channel \" + event.getChannel()\n                    + \" with unique id \" + event.getUniqueId());\n            return;\n        }\n```\n\n\nThis is normal though because Dial Events aren't expected to have a source channel when created via an originate (we do a lot of origination via AMI).\n\nMy suggestion would be to axe this check/warning entirely and make all the sourceChannel stuff further down\nthis function require that sourceChannel not be null instead.","author":{"url":"https://github.com/JonathanRRose","@type":"Person","name":"JonathanRRose"},"datePublished":"2025-04-21T15:15:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/708/asterisk-java/issues/708"}