F on the end of the number

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Removing the F on sent numbers is very simple.

Original code:
void isup_set_called(struct isup_call *c, const char *called, unsigned 
char called_nai, const struct ss7 *ss7)
{
         if (called && called[0]) {
                 if (ss7->switchtype == SS7_ITU)
                         snprintf(c->called_party_num, 
sizeof(c->called_party_num), "%sF", called);
                 else
                         snprintf(c->called_party_num, 
sizeof(c->called_party_num), "%s", called);
                 c->called_nai = called_nai;
         }

}

Modified code:
void isup_set_called(struct isup_call *c, const char *called, unsigned 
char called_nai, const struct ss7 *ss7)
{
         if (called && called[0]) {
                 snprintf(c->called_party_num, 
sizeof(c->called_party_num), "%s", called);
                 c->called_nai = called_nai;
         }
}

On chan_ss7 this is a configuration file option.
On 07/26/12 13:25, Kaloyan Kovachev wrote:
> On Thu, 26 Jul 2012 12:54:58 -0300, Gustavo M?rsico
> <gustavomarsico at gmail.com> wrote:
>> I faced a similar issue recently and was related to the Screening
>> Indicator. Was solved adding before Dial the following line:
>>
>> Set(CALLERPRES()=allowed) or Set(CALLERPRES()= prohib)
>>
>> In both cases the important was the 2 bits saying "network provided".
>>
>> Hope this helps.
>>
>>
>> On Jul 26, 2012, at 12:29 PM, Marcus Vinicius wrote:
>>
>>> Hi Kaloyan,
>>>
>>> If I change ss7type=ansi the link doens't work:
>>>
>>> [Jul 26 11:05:43] ERROR[637]: chan_dahdi.c:13836 dahdi_ss7_error: [3]
>>> Received message destined for point code 0x37c372 but we're 0x372.
>>> Dropping
>>>
>>> The ERICSSON uses ITU standard as well. It uses ITU/ISUP BRAZIL.
>>>
>>> But the Ericsson doesn't understand the F on the number.
> Not sure about the Brazil variant, but ITU-T Q.764 defines the en-block
> dialing to end with ST.
> 0xf is ST signal it means 'end of dialing' or 'number is complete', so it
> should understand it and your problem is probably somewhere else.
>
> As Johann Steinwendtner have noted you receive the number without leading
> 0, but you send it with 0 - this or as Gustavo suggested
> Screening/Presentation may be the problem.
>
>>>> Can I disable this F ?
>>>>
>>>> Is it hardcode? Anyone knows how can I change this?
>>>>
> Yes, it is hardcoded for ITU switchtype - check isup.c isup_set_called().
> You may try to modify the code, but i don't think that this is the problem.
>
>>>> Thank you so much!
>>>>
>>>>
>>>> --
>>>> Marcus Vinicius
>>>
>>> --
>>> _____________________________________________________________________
>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>>
>>> asterisk-ss7 mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>    http://lists.digium.com/mailman/listinfo/asterisk-ss7
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
>     http://lists.digium.com/mailman/listinfo/asterisk-ss7





[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux