DISCONNECT:cause value:invalid message incompatible destination

[lindelott]

hi all

i receive this message every time and ONLY when i call a national number 06xxxxxxxx trough a PRI FW with my MXONE TSE5.0 SP6 in overlap selection (i can't make enbloc sending now )
in my trace i see a setup message incomplete,the answer setup ack from network and a series of INFORMATION that i send to the nerwork completing the number,number absolutely correct...i see
but instead of alerting message i receive a disconnect message with that cause
any idea?
Denny

 

[lindelott]

I try to attach the trace hoping somebody could help me...


Outgoing Message: SETUP
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol



BEARER CAPABILITY IE:
Coding Standard: CCITT standardized
Information Transfer Capability: 3.1 kHz audio
Transfer Mode: Circuit-mode Call independent signalling connection
Information Transfer RateCircuit Mode: 64 kbits
Layer 1 Protocol Identification: User information layer 1 protocol
Recommendation G.711 A-law


CHANNEL ID IE:
Interface Identifier Present: Interface implicitly identified; the interface which includes the D-channel carrying this information element is indicated.
Interface Type: Primary rate interface
PreferredExclusive: Indicated channel is preferred
D-channel Indicator: The channel identified is not the D-channel
Information Channel SelectionPrimary Interface: As in following octets
Coding Standard: CCITT standard
Number: Channel is indicated by the number in the following octet
Channel Type: B-channel units
Channel number: 19


CALLING PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: ISDN numbering plan
Presentation Indicator: Presentation Restricted
Spare, reserved
Screening Indicator: User provided, not screened
Calling Party Number: 3048



CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: 068


Incoming Message: SETUP ACKnowledgement
Call Reference: 5D 9D (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol



CHANNEL ID IE:
Interface Identifier Present: Interface implicitly identified; the interface which includes the D-channel carrying this information element is indicated.
Interface Type: Primary rate interface
PreferredExclusive: Exclusive; only the indicated channel is acceptable
D-channel Indicator: The channel identified is not the D-channel
Information Channel SelectionPrimary Interface: As in following octets
Coding Standard: CCITT standard
Number: Channel is indicated by the number in the following octet
Channel Type: B-channel units
Channel number: 19


Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: 0


Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: 9





>>>>
Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: 8


Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: X


Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: X




Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: X




Outgoing Message: INFOrmation
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol




CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: X


Incoming Message: DISConnect
Call Reference: 5D 9D (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol



CAUSE IE:
Coding Standard: CCITT standard
Location: User
Cause Value: Invalid message
Cause Values, CCITT Standard: Incompatible destination


PROGRESS INDICATOR IE:
Coding Standard: CCITT standard
Location: Local network
Progress Description: In-band information or an appropriate pattern is now available


Outgoing Message: RELease
Call Reference: 5D 9D (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol



CAUSE IE:
Coding Standard: CCITT standard
Location: Local private network eg PBX
Cause Value: Invalid message
Cause Values, CCITT Standard: Incompatible destination


Incoming Message: RELease COMplete
Call Reference: 5D 9D (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol


I masked for privacy the last four digit ;P
Denny

 

[snor]

Hi,
there might be 3 possible reasons, why call is disconnected:
1.) Destination do not accept your "3.1 kHz audio" call. (maybe only "speech" is accepted)
2.) Destination needs the "A-number" of the calling party (see your calling party IE : Presentation Restricted)
3.) Destination do not accept "overlap sending", only "block sending" with "sending complete"
(how many seconds are between the last INFORMATION-Element and the DISCONNECT-Message ? (0 sec., 4 sec. or 10 sec.?)
best regards,
Norbert

 

[lindelott]

thank you Norbert
I'll try and i'll let you know

Denny

 

[lindelott]

RESOLVED

FYI

"If national ISDN is used and the market is Italy the following applies

1) If the calling party is an analogue extension the call should be “3.1 kHz”.
2) If the calling party is anything else like digital the call should be “speech”.

In SLP60 (5.0 SP6 and maybe earlier) there is a fault so SLP60 always believe that the calling party is analogue hence coding “3.1 kHz” in the SETUP of the call."

Denny