[asterisk-bugs] [JIRA] (SS7-58) Lost final digits in Called Party Number

[adomjan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/SS7-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203549#comment-203549 ] 

adomjan commented on SS7-58:
----------------------------

I think it is a limit of the length of the variable length parameter.

your nature of address is national...

set in chan_dahdi.conf: 
ss7_internationalprefix=00

asterisk will remove 00 prefix and will set 4 to Nature of address (international)



                
> Lost final digits in Called Party Number
> ----------------------------------------
>
>                 Key: SS7-58
>                 URL: https://issues.asterisk.org/jira/browse/SS7-58
>             Project: LibSS7
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>         Environment: Dahdi 2.6 - Asterisk 1.8 - LibSS7 1.0.2
>            Reporter: Oscar Aldana
>            Assignee: mattf
>
> I recently installed and configured the libss7 library on a server with Asterisk 1.8, work perfect but would like to help me solve a question that I have about incoming calls, I have a problem when entering Called Party Number (Num B) calls with more than 15 digits, asterisk recognizes only 15 and the rest of the number is lost.
> As I understand after 15 digits creates another variable to store the rest of the Called Party Number. How I can complete the number?
> Example:
> Real number Dialed:00486123456789012
> Debug Show:
> --VARIABLE LENGTH PARMS[1]--
> Called Party Number:
>   Nature of address: 3
>   NI: 1
>   Numbering plan: 1
>   Address signals: 0048612345678901
>   [ 0a 03 90 00 84 16 32 54 76 98 10 ]
> Linkset 1: Processing event: ISUP_EVENT_IAM
>     -- Accepting call to '0048612345678901' on CIC 2
>     -- Executing [0048612345678901 at ss7:1] NoOp("DAHDI/2-1", "16167069") in new stack
> Again I appreciate your help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira