[asterisk-bugs] [JIRA] (ASTERISK-14274) LibSS7 not working when linkset is set to a value > 2
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Thu Feb 26 08:39:34 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-14274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-14274:
-----------------------------------
Description:
I am using LibSS7 with Asterisk 1.6.0.9. The problem is that when I set the linkset to a value greater than 2 the outgoing and incoming calls fail due to incorrect number formating saying: Incomplete address.
The libss7 does not set the correct numbering plan. The link is up and everythink else seems ok.
This is the debug from a configuration with linkset with value <=2 which is a successfull call from 222222 to 111111:
{noformat}
Category: Ordinary calling subscriber (10)
[ 0a ]
Transmission Medium Requirements:
Speech (0)
[ 00 ]
--VARIABLE LENGTH PARMS[1]--
Called Party Number:
Nature of address: 3
NI: 0
Numbering plan: 1
Address signals: 111111#
[ 07 03 10 76 02 62 60 f7 ]
--OPTIONAL PARMS--
Calling Party Number:
Nature of address: 3
NI: 0
Numbering plan: 1
Presentation: 0
Screening: 1
Address signals: 222222
[ 0a 06 03 11 44 03 00 90 ]
{noformat}
This is the debug from a configuration with linkset with value > 2 which is a failed call from 222222 to 111111:
{noformat}
Calling Party's Category:
Category: Ordinary calling subscriber (10)
[ 0a ]
Transmission Medium Requirements:
Speech (0)
[ 00 ]
--VARIABLE LENGTH PARMS[1]--
Called Party Number:
Nature of address: 0
NI: 0
Numbering plan: 1
Address signals: 111111#
[ 08 80 10 60 27 20 06 76 0f ]
--OPTIONAL PARMS--
Calling Party Number:
Nature of address: 0
NI: 0
Numbering plan: 1
Presentation: 0
Screening: 1
CLI> Address signals: 222222
Cause Indicator:
Coding Standard: 0
CLI> Location: 2
Cause Class: 1
Cause Subclass: 12
CLI> Cause: Invalid number format (address incomplete) (28)
{noformat}
was:
I am using LibSS7 with Asterisk 1.6.0.9. The problem is that when I set the linkset to a value greater than 2 the outgoing and incoming calls fail due to incorrect number formating saying: Incomplete address.
The libss7 does not set the correct numbering plan. The link is up and everythink else seems ok.
This is the debug from a configuration with linkset with value <=2 which is a successfull call from 222222 to 111111:
Category: Ordinary calling subscriber (10)
[ 0a ]
Transmission Medium Requirements:
Speech (0)
[ 00 ]
--VARIABLE LENGTH PARMS[1]--
Called Party Number:
Nature of address: 3
NI: 0
Numbering plan: 1
Address signals: 111111#
[ 07 03 10 76 02 62 60 f7 ]
--OPTIONAL PARMS--
Calling Party Number:
Nature of address: 3
NI: 0
Numbering plan: 1
Presentation: 0
Screening: 1
Address signals: 222222
[ 0a 06 03 11 44 03 00 90 ]
This is the debug from a configuration with linkset with value > 2 which is a failed call from 222222 to 111111:
Calling Party's Category:
Category: Ordinary calling subscriber (10)
[ 0a ]
Transmission Medium Requirements:
Speech (0)
[ 00 ]
--VARIABLE LENGTH PARMS[1]--
Called Party Number:
Nature of address: 0
NI: 0
Numbering plan: 1
Address signals: 111111#
[ 08 80 10 60 27 20 06 76 0f ]
--OPTIONAL PARMS--
Calling Party Number:
Nature of address: 0
NI: 0
Numbering plan: 1
Presentation: 0
Screening: 1
CLI> Address signals: 222222
Cause Indicator:
Coding Standard: 0
CLI> Location: 2
Cause Class: 1
Cause Subclass: 12
CLI> Cause: Invalid number format (address incomplete) (28)
> LibSS7 not working when linkset is set to a value > 2
> -----------------------------------------------------
>
> Key: ASTERISK-14274
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-14274
> Project: Asterisk
> Issue Type: Bug
> Components: Channels/chan_dahdi, Channels/chan_dahdi/SS7
> Reporter: Gentian Bajraktari
>
> I am using LibSS7 with Asterisk 1.6.0.9. The problem is that when I set the linkset to a value greater than 2 the outgoing and incoming calls fail due to incorrect number formating saying: Incomplete address.
> The libss7 does not set the correct numbering plan. The link is up and everythink else seems ok.
> This is the debug from a configuration with linkset with value <=2 which is a successfull call from 222222 to 111111:
> {noformat}
> Category: Ordinary calling subscriber (10)
> [ 0a ]
> Transmission Medium Requirements:
> Speech (0)
> [ 00 ]
> --VARIABLE LENGTH PARMS[1]--
> Called Party Number:
> Nature of address: 3
> NI: 0
> Numbering plan: 1
> Address signals: 111111#
> [ 07 03 10 76 02 62 60 f7 ]
> --OPTIONAL PARMS--
> Calling Party Number:
> Nature of address: 3
> NI: 0
> Numbering plan: 1
> Presentation: 0
> Screening: 1
> Address signals: 222222
> [ 0a 06 03 11 44 03 00 90 ]
> {noformat}
> This is the debug from a configuration with linkset with value > 2 which is a failed call from 222222 to 111111:
> {noformat}
> Calling Party's Category:
> Category: Ordinary calling subscriber (10)
> [ 0a ]
> Transmission Medium Requirements:
> Speech (0)
> [ 00 ]
> --VARIABLE LENGTH PARMS[1]--
> Called Party Number:
> Nature of address: 0
> NI: 0
> Numbering plan: 1
> Address signals: 111111#
> [ 08 80 10 60 27 20 06 76 0f ]
> --OPTIONAL PARMS--
> Calling Party Number:
> Nature of address: 0
> NI: 0
> Numbering plan: 1
> Presentation: 0
> Screening: 1
> CLI> Address signals: 222222
> Cause Indicator:
> Coding Standard: 0
> CLI> Location: 2
> Cause Class: 1
> Cause Subclass: 12
> CLI> Cause: Invalid number format (address incomplete) (28)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list