The traces indicate the cause value of 65 in Q.850 which states "Bearer
capability not implemented".
This means UAS didn't like one of the fields in the following:
Access transport (9 bytes length)
Optional Parameter: 3 (Access transport)
Parameter length: 9
Access transport parameter field (-> Q.931)
Progress indicator
Information element: Progress indicator
Length: 2
.00. .... = Coding standard: ITU-T standardized
coding (0x00)
Location: User (U)
Progress description: Origination address is
non-ISDN
Low-layer compatibility
Information element: Low-layer compatibility
Length: 3
1... .... = Extension indicator: last octet
.00. .... = Coding standard: ITU-T standardized
coding (0x00)
...1 0000 = Information transfer capability: 3.1
kHz audio (0x10)
1... .... = Extension indicator: last octet
.00. .... = Transfer mode: Circuit mode (0x00)
...1 0000 = Information transfer rate: 64 kbit/s
(0x10)
1... .... = Extension indicator: last octet
...0 0011 = User information layer 1 protocol:
Recommendation G.711 A-law (0x03)
User service information, (3 bytes length)
Optional Parameter: 29 (User service information)
Parameter length: 3
User service information (-> Q.931 Bearer_capability)
1... .... = Extension indicator: last octet
.00. .... = Coding standard: ITU-T standardized coding
(0x00)
...1 0000 = Information transfer capability: 3.1 kHz
audio (0x10)
1... .... = Extension indicator: last octet
.00. .... = Transfer mode: Circuit mode (0x00)
...1 0000 = Information transfer rate: 64 kbit/s (0x10)
1... .... = Extension indicator: last octet
...0 0011 = User information layer 1 protocol:
Recommendation G.711 A-law (0x03)
Basically the incoming BC has to match with the BC which the UAS supports. I
have attached the request packet for which the 488 response is generated.
Hope this helps,
Somesh
-----Original Message-----
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext Brett
Tate
Sent: Monday, July 04, 2011 4:53 PM
To: Verma, Salil (NSN - IN/Gurgaon); sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] error 488
Would need to see the request to provide more details.
> We are getting this cause Reason: Q.850;cause=65
<snip>
> We are getting error 488 (not acceptable media ) when
> ever we make a call.
>
> Any suggestion .
The following is a snippet from RFC 3398 section 7.2.4.1 ISDN Cause Code to
Status Code Mapping.
ISUP Cause value SIP response
---------------- ------------
65 bearer capability not implemented 488 Not Acceptable Here
The following is a snippet from Q.850.
http://www.itu.int/rec/T-REC-Q.850/e
2.2.7.4 Service or option not implemented class
2.2.7.4.1 Cause No. 65 - Bearer capability not implemented
This cause indicates that the equipment sending this cause does not support the
bearer capability requested.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
