[Home]

Summary:ASTERISK-17235: hint for confbridge fails
Reporter:Sean Darcy (seandarcy)Labels:
Date Opened:2011-01-19 13:15:45.000-0600Date Closed:2011-06-07 14:04:49
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:See issue 0018518.

As in above, I'm trying to move from MeetMe to ConfBridge. I've now installed 1.8.2.1. Same problem.

I have set hints:

[blf]
exten => 80,hint,ConfBridge:80
exten => 81,hint,ConfBridge:81
exten => 82,hint,ConfBridge:82
exten => 83,hint,ConfBridge:83
exten => 84,hint,ConfBridge:84

yet no blf on ConfBridge:

   -- Executing [81@longdistance:1] Answer("SIP/144-0000003d", "") in new stack
   -- Executing [81@longdistance:2] ConfBridge("SIP/144-0000003d", "81") in new stack
   -- <SIP/144-0000003d> Playing 'conf-onlyperson.ulaw' (language 'en')


****** ADDITIONAL INFORMATION ******

When I'm in the ConfBridge 81, core show hints has ConfBridge 81 idle:

.........
178@blf                : SIP/178               State:Idle            Watchers  3
84@blf                 : ConfBridge:84         State:Idle            Watchers  9
140@blf                : SIP/140               State:Idle            Watchers  3
81@blf                 : ConfBridge:81         State:Idle            Watchers  9
80@blf                 : ConfBridge:80         State:Idle            Watchers  0
142@blf                : SIP/142               State:InUse           Watchers  3
83@blf                 : ConfBridge:83         State:Idle            Watchers  9
82@blf                 : ConfBridge:82         State:Idle            Watchers 11
............

blf works for ringing, in use, etc.
Comments:By: Clod Patry (junky) 2011-01-27 15:56:13.000-0600

hi,
like you can see in the CHANGEs file, you must use:
exten => 80,hint,confbridge:80  (all lowercase) to get it works.

tested with: Asterisk 1.8.2.3


snip from CHANGES:
* Added custom device states to ConfBridge bridges.  Use 'confbridge:<name>' to
  retrieve state for a particular bridge, where <name> is the conference name


Confirm me everything works fine for you so we can close this ticket.

Thanks
By: Sean Darcy (seandarcy) 2011-01-28 00:50:28.000-0600

Changed confbridge to all lower case:

exten => 84,hint,confbridge:84

core show hints lists it:
84@blf             : confbridge:84         State:Idle            Watchers  9

but if I enter the bridge:

Answer("SIP/sip-000002fe", "") in new stack
ConfBridge("SIP/sip-000002fe", "84") in new stac

core show hints still shows 84 idle:

84@blf            : confbridge:84         State:Idle            Watchers  9

sean
By: Birger "WIMPy" Harzenetter (wimpy) 2011-01-28 06:41:35.000-0600

It worked for me after changing to all lower case.
By: Clod Patry (junky) 2011-01-28 09:28:38.000-0600

seandarcy: you have to put your peer 'sip' in the blf context (or with an include).


By: Sean Darcy (seandarcy) 2011-01-30 17:27:37.000-0600

I'm afraid you've lost me.

Here's my blf context:

[blf]
exten => 81,hint,MeetMe:81
;;exten => 82,hint,MeetMe:82
exten => 82,hint,confbridge:82
;;exten => 83,hint,MeetMe:83
exten => 83,hint,confbridge:83
exten => 170,hint,SIP/170
exten => 164,hint,SIP/164
...............

[conferences]
exten=>81,1,Meetme(81,1Ms,1234)
exten=>_8[2-9],1,Answer()
;;exten=>_8[1-9],1,Meetme(${EXTEN},1Ms,1234)
exten=>_8[2-9],n,NoOp("Using lowercase confbridge")
exten=>_8[2-9],n,confbridge(${EXTEN})


If I dial 81 from any peer, MeetMe generates a blf:

   -- Executing [81@conferences:1] MeetMe("SIP/sip-000003eb", "81,1Ms,1234") in new stack
 == Parsing '/etc/asterisk/meetme.conf':   == Found
   -- Created MeetMe conference 1023 for conference '81'
 == Extension Changed 81[blf] new state InUse for Notify User 169
 == Extension Changed 81[blf] new state InUse for Notify User 176
.........
> core show hints

81@blf                 : MeetMe:81             State:InUse           Watchers  9

But confbridge does not generate a hint from the _same_ blf context:
-- Executing [82@conferences:1] Answer("SIP/sip-000003ed", "") in new stack
   -- Executing [82@conferences:2] NoOp("SIP/sip-000003ed", ""Using lowercase confbridge"") in new stack
   -- Executing [82@conferences:3] ConfBridge("SIP/sip-000003ed", "82") in new stack
core show hint 82
    82@blf           : confbridge:82         State:Idle            Watchers 11
1 hint matching extension 82

So the blf context works for MeetMe, without having the "sip" peer in the context. In fact, I don't even know how I would include a SIP peer in a dialing plan context. Much less how to do that for every possible user of confbridge.
By: Sean Bright (seanbright) 2011-01-31 09:34:10.000-0600

I just tested this with the latest from the 1.8 branch:

$ cat /etc/asterisk/extensions.conf
[blf]
exten => 82,hint,confbridge:82
exten => 83,hint,confbridge:83
exten => 84,hint,confbridge:84
exten => 85,hint,confbridge:85
exten => 86,hint,confbridge:86
exten => 87,hint,confbridge:87
exten => 88,hint,confbridge:88
exten => 89,hint,confbridge:89

[conferences]
exten => _8[2-9],1,Answer(2000)
exten => _8[2-9],n,ConfBridge(${EXTEN})

And the test:
== Using SIP RTP CoS mark 5
-- Executing [84@conferences:1] Answer("SIP/meh-00000000", "2000") in new stack
-- Executing [84@conferences:2] ConfBridge("SIP/meh-00000000", "84") in new stack
-- <SIP/meh-00000000> Playing 'conf-onlyperson.gsm' (language 'en')

*CLI> core show hint 84
                    84@blf                 : confbridge:84         State:InUse           Watchers  0
1 hint matching extension 84
By: Clod Patry (junky) 2011-01-31 10:30:21.000-0600

so, everything seems to be all right now.
Let's close this one.
By: Sean Bright (seanbright) 2011-01-31 14:48:09.000-0600

I would prefer to get confirmation from the reporter that he is able to get it to work in his environment before we close this.  There may be a problem specific to his setup.
By: Sean Darcy (seandarcy) 2011-02-01 20:56:18.000-0600

Well, it doesn't WFM.

   -- Executing [81@conferences:1] MeetMe("SIP/sip-00000514", "81,1Ms,1234") in new stack
 == Parsing '/etc/asterisk/meetme.conf':   == Found
   -- Created MeetMe conference 1023 for conference '81'
 == Extension Changed 81[blf] new state InUse for Notify User 176
 == Extension Changed 81[blf] new state InUse for Notify User 169
........
core show hint 81
  81@blf            : MeetMe:81             State:InUse           Watchers  9

BUT:
   -- Executing [83@conferences:1] Answer("SIP/sip-00000515", "") in new stack
   -- Executing [83@conferences:2] NoOp("SIP/sip-00000515", ""Using lowercase confbridge"") in new stack
   -- Executing [83@conferences:3] ConfBridge("SIP/sip-00000515", "83") in new stack
PBX*CLI> core show hint 83
83@blf            : confbridge:83         State:Idle            Watchers  9

See the dialplan above. BTW, also tried with Answer(2000) to match seanbright. No joy. I've tried with and without subscribecontext = blf in sip.conf.

Can't imagine why it works for you guys, and not for me.
By: Sean Bright (seanbright) 2011-02-02 06:28:37.000-0600

And you're using the latest 1.8 from SVN or still 1.8.2.1?
By: Sean Darcy (seandarcy) 2011-02-02 10:58:49.000-0600

core show version
Asterisk 1.8.2.2

Is there a change in svn? 1.8.3-rc2?
By: Clod Patry (junky) 2011-02-02 11:26:44.000-0600

seandarcy: i've sent ya an email to ur gmail.
I really suspect a config issue here.
By: Sean Bright (seanbright) 2011-02-02 13:08:12.000-0600

junky: what do you think the configuration issue is?

seandarcy: there are 42 commits since 1.8.2.2 was tagged, but I'm not sure any of them affect this issue.  I will test with 1.8.2.2.

<b>EDIT:</b> I'm able to get this to work with the same config that I was using with 1.8 from SVN.

I'm baffled on this one, I may need to see more of your configuration/get remote access to your machine?  Whichever you prefer.


By: Sean Darcy (seandarcy) 2011-02-02 15:48:53.000-0600

Got today's svn, 305796.

That works! Let's hope it's in 1.8.3.

Thanks for the help.
By: Sean Darcy (seandarcy) 2011-02-02 15:56:37.000-0600

BTW, got branch 1.8, not trunk.
By: Clod Patry (junky) 2011-02-02 16:07:16.000-0600

Yes, that will be in 1.8.3

Thanks.