[Asterisk-Users] Don't know what to do if second ROSE component is of type 0x6

[William Lloyd]

I also have the same problem at a customer.  It's PRI setup as 5ESS.

It doesn;t seem to be hurting anything but it is related to the caller 
ID.  I tried google for docs etc but I came up with nothing I could 
understand or figure out.

Over time I've used both Sangoma and Digium card and it appears with 
both. I've mostly been running CVS head at this location for several 
months.  The problem still exists in CVS head from around 2 weeks ago.

The situation seems related to 800 number inbound only.  I have some PRI 
debug traces where I can call the PRI from my house using the toll free 
800 number that is routed to the PRI.  I get the second rose 6 error.  
When I dial the local pilot line that feeds into the PRI the call comes 
through with no error message.  The only difference is the number I use 
to call the PRI.  800 toll free vs local number. 

It also seems to affect the Caller ID name.  Caller ID number comes 
throug in both cases.  Caller ID Name doesn;t seem to show up when I get 
a Rose 6 error.

I was hoping to put the two traces up next to each other and see what's 
coming down the D channel differently in the two situations but so far I 
havn;t had the time...

-bill



Jeremy Gault wrote:

> FWIW, we are also seeing this message each time we receive a call.  I 
> also went the Google route and found only questions, not answers.  We 
> are running a PRI from US LEC (channels 1-10 are B-channels, with 
> channel 24 being the D-channel, and we are only running voice on the 
> PRI.)  The PRI is connected directly to our Digium TE110P card, and 
> obviously we are using the zaptel drivers.
>
> We did not see this message when running */zaptel/libpri 1.0.9.  
> However, after upgrading (we went to 1.2.0-beta1 and now to CVS) we 
> started seeing the message.  (I don't remember exactly if we saw it in 
> the beta, but we do in the CVS.)
>
> In our case, it does not seem to affect the stability of our * 
> machine.  (However, bear in mind that you may be using parts of * that 
> we do not, and the problem could lie in those parts.)  We're handling 
> all PSTN calls via the PRI, except outbound to toll-free which are 
> handed off to an IAX gateway on the Internet.  Our employees' desks 
> are connected via the LAN (using Polycom 500/501 SIP phones.)  I have 
> a remote extension at home (also SIP) using a Sipura SPA-2000.
>
> We did have some stability issues (Asterisk would segfault) when we 
> first moved to CVS.  Of course, safe_asterisk handled this and a 
> couple of days later we updated again from CVS and it seemed to fix 
> the stability issue we were having.
>
> If you are using CVS (but not the latest one) you may want to try 
> upgrading.
>
> I wouldn't worry about that message, though.  However, I would also be 
> interested in knowing what it means/what causes it. :)
>
>          Jeremy
>
> Tom Rymes wrote:
>
>> Has anyone figured out what this message means:
>>
>> Don't know what to do if second ROSE component is of type 0x6
>>
>> We are running a PRI through a Sangoma card that is handling the
>> D-channel natively at this point, but we go the error when zaptel was
>> handling the D-channel, too. I have googled, but all of the messages are
>> like this one with no answers that I can find. It's probably a
>> non-issue, but we have been having issues with stability of our *
>> install and I'd like to figure this out!
>>
>