[cisco-voip] Facility IE cnam delivery and SIP

[Brian Meade (brmeade)]

Ahh, It looks like I only saw the Status in your debug.  Looking further down at your facility message, I think this is the issue.  5ESS switches shouldn't be using Facility for calling name- https://supportforums.cisco.com/thread/2038757



-----Original Message-----
From: Adam Pawlowski [mailto:ajp26 at acsu.buffalo.edu] 
Sent: Friday, October 18, 2013 2:13 PM
To: Brian Meade (brmeade); Pawlowski, Adam; cisco-voip at puck.nether.net
Subject: RE: Facility IE cnam delivery and SIP

Brian,

     I'm reading that as us sending that towards the carrier switch, if I set as national it will not transmit that message upon receiving the facility IE, it instead breaks it out and processes it. I'm reading that this is as per 5ESS specifications, caller name shouldn't be sent in a facility message, so it's not something that IOS would process when treating it as a 5E, thus the error. If that's really the case I suppose I don't expect it to be a real bug and repairable, but I am no ISDN pro - that's for sure.

Adam 


> -----Original Message-----
> From: Brian Meade (brmeade) [mailto:brmeade at cisco.com]
> Sent: Friday, October 18, 2013 2:06 PM
> To: Adam Pawlowski; Pawlowski, Adam; cisco-voip at puck.nether.net
> Subject: RE: Facility IE cnam delivery and SIP
> 
> It looks like you're received that message from the carrier in 
> response to sending a STATUS.  I'm guessing the carrier switch is 
> hitting something
like
> CSCsj03558.  Here's a snippet of the logs from that bug:
> 
> " May  7 10:26:16.032 EDT: ISDN Se1/0:23 Q931: RX <- STATUS pd = 8
callref =
> 0x02
> A0
> 	Cause i = 0x83E203 - Message not compatible with call state or not 
> imple mented
> 	Call State i = 0x07"
> 
> Brian
> 
> -----Original Message-----
> From: Adam Pawlowski [mailto:ajp26 at acsu.buffalo.edu]
> Sent: Friday, October 18, 2013 1:53 PM
> To: Brian Meade (brmeade); Pawlowski, Adam; cisco-voip at puck.nether.net
> Subject: RE: Facility IE cnam delivery and SIP
> 
> Brian,
> 
>      Yes, it seems to be for Facility messages, there's a snippet below.
It spits a
> similar error to what is listed in that bug when set as 5ESS. If I set 
> it
to NI then
> it seems to understand these messages and it operates properly, but it
stops
> working after some time so there are other incompatibilities. It does 
> work
as
> MGCP backhauled to a UCM so it would appear the carrier's signaling is
valid.
> This is on a 2921 running 15.1(4)M4. I had not upgraded past this 
> point as
I
> had seen a number of bugs appear regarding ISDN PRI calls and 
> crashing,
and
> everything is working otherwise at the moment.
> 
> Adam
> 
> Oct 18 13:49:17 Est-Std: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8
callref =
> 0x822D Oct 18 13:49:18 Est-Std: ISDN Se0/0/0:23 Q931: RX <- FACILITY 
> pd =
8
> callref = 0x022D
>         Facility i =
> 0x9F8B0100A117020101020100800F552042554646414C4F20202020202
> 0
> Oct 18 13:49:18 Est-Std: ISDN Se0/0/0:23 **ERROR**: Ux_BadMsg: Invalid 
> Message f or call state 7, call id 0x87B, call ref 0x822D, event 0x62 
> Oct
18
> 13:49:18 Est-Std: ISDN Se0/0/0:23 Q931: TX -> STATUS pd = 8  callref = 
> 0x
822D
>         Cause i = 0x80E262 - Message not compatible with call state or 
> not
imple
> mented
>         Call State i = 0x07
> 
> > -----Original Message-----
> > From: Brian Meade (brmeade) [mailto:brmeade at cisco.com]
> > Sent: Friday, October 18, 2013 1:30 PM
> > To: Pawlowski, Adam; cisco-voip at puck.nether.net
> > Subject: RE: Facility IE cnam delivery and SIP
> >
> > Adam,
> >
> > Is this for incoming Facility messages from the carrier?
> >
> > I did find CSCsi19946 which added 5ESS support to incoming 
> > facilities in a
> call
> > active state but it seems to be fixed in most later 12.4 versions.
> >
> > Brian
> >
> > -----Original Message-----
> > From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On 
> > Behalf Of Pawlowski, Adam
> > Sent: Friday, October 18, 2013 11:20 AM
> > To: cisco-voip at puck.nether.net
> > Subject: [cisco-voip] Facility IE cnam delivery and SIP
> >
> > Just wanted to check with the list, as I can't really find the 
> > information
> on this
> > but, Facility IE based CNAM delivery for ISDN PRI is still not 
> > supported
> with
> > SIP  and the 5ESS?
> >
> > When I enable signaling forwarding I just end up returning Message 
> > not compatible with call state or not implemented and terminating the call.
> >
> > Apparently it works for H323 but there is allusion that it works for 
> > SIP
> in a few
> > places, but it appears not. I'd rather not bother the telco for this 
> > as
> it's not
> > particularly important, but just curious. I found that if I set it 
> > to
> primary-ni it
> > will work for a while but then falls apart after some time as others 
> > have noted.
> >
> > Thanks,
> >
> > Adam Pawlowski
> > SUNYAB
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>