[asterisk-bugs] [JIRA] (ASTERISK-27297) ChanSpy attaching to wrong Channel with similar Name

[Michael Balen (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238912#comment-238912 ] 

Michael Balen edited comment on ASTERISK-27297 at 9/28/17 4:06 AM:
-------------------------------------------------------------------

Oops, you are right, sometimes it can be useful to read the fine manual ;-)
Please close this..sorry



was (Author: aeinstein):
Oops, you are right, but this behavier sucks. 
Now I have to define hundreds of Spygroups, each per customer....
Please close this..sorry


> ChanSpy attaching to wrong Channel with similar Name
> ----------------------------------------------------
>
>                 Key: ASTERISK-27297
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27297
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_chanspy
>    Affects Versions: 13.16.0
>         Environment: PJSIP
>            Reporter: Michael Balen
>            Assignee: Alexander Anikin
>
> ChanSpy attaching to Channel PJSIP/101 when request PJSIP/10 and 101 is on call. Only if all channels PJSIP/10* are not on call it connects to the right Channel. 
> When I request PJSIP/22 it connects for example to PJSIP/225 if there is a call. 
> I think it takes the first matching channelname for the length of the requested channelname. 
> more Examples
> 10 -> 105
> 24 -> 124
> and so on.
> Executing [887PJSIP-10 at diag:3] ChanSpy("PJSIP/livemonitor-0000d57d", "PJSIP/10,qd") in new stack
>   == Spying on channel PJSIP/101-0000cbf2
> [Sep 26 16:46:15] NOTICE[11729][C-000173d2]: app_chanspy.c:504 start_spying: Attaching PJSIP/livemonitor-0000d57d to PJSIP/101-0000cbf2



--
This message was sent by Atlassian JIRA
(v6.2#6252)