[Iaxclient-devel] Re: iaxcomm iaxclient registry problem

[Steve K. <st...@st...>]

Stephan,

    Can you (or have you already) faxed in a disclaimer to digium for 
your libiax2 changes?

    If you have, than I'd gladly take this change and send it up to Digium.

    As far as your alignment patch, I guess my questions are:

1) First, the patches are definitely not needed for all RISC platforms; 
the code works just fine on PPC, for example.

2) Why haven't others who are using iaxclient on zaurus running into 
this same problem?

That patch seems like a lot of clutter to add to the code if it isn't 
really necessary..

-SteveK


S wrote:

> Hi Steve,
>
> I found the registry bug in the libiax2/src/iax2.c,
> In function iax_header_to_event(...) is no POKE command handle, so I 
> add this line and it work (only POKE case section) :
>
>             case IAX_COMMAND_PING:
>                 /* Just immediately reply */
>                 e->etype = IAX_EVENT_PING;
>                 e->ts = ts;
>                 e = schedule_delivery(e, ts);
>                 break;
>             case IAX_COMMAND_POKE: /* SKA fix registry problem */
>                 send_command_immediate( session,
>                                         AST_FRAME_IAX,
>                                         IAX_COMMAND_PONG,
>                                         ts, NULL, 0, fh->iseqno);
>                 e = NULL;
>                 break;
>             case IAX_COMMAND_PONG:
>
> Please add the POKE case section to libiax2/src/iax2.c line 2119
>
> iax2 show peers
> skaAtHome  172.16.16.160   (D)  255.255.255.255  4569      OK (22 ms)
>
> I suspect there is still a other bug, because afer a while ( and 4 
> times refreshing registration ) I get a UNREACHABLE and a while later 
> I get a REACHABLE
>
> Regards
>
>   Stephan
>
> PS : This is the next stop to iax phone on a ARM RISC Zaurs PDA.
> PS : There are still some align patches for iax2-parser.c out...
>
>
>
> S wrote:
>
>> Hi IAX Guru's,
>>
>> I have the problem to register a iaxclient (iaxcomm or my own Zaurus 
>> client) to asterisk.
>> Here is my observation on asterisk with iax2 debug on where a 
>> iaxclient try to register :
>>
>> Rx --> REGREQ
>> TX <-- REGAUTH
>> Rx --> REGREQ
>> TX <-- POKE
>> TX <-- REGACK
>> RX --> ACK
>> RX --> ACK
>> TX <--POKE
>>
>> iax2 show peers
>> Name/Username    Host                 Mask             Port  Status
>> muggel/muggel    (Unspecified)   (D)  255.255.255.255  0    UNKNOWN
>> skaAtHome        172.16.16.160   (D)  255.255.255.255  4569 UNREACHABLE
>> ska/ska          (Unspecified)   (D)  255.255.255.255  0    UNKNOWN
>>
>>
>> And here is the iax2 debug while one asterisk register on a second one.
>> RX --> REGREQ
>> TX <-- REGAUTH
>> RX --> REGREQ
>> TX <-- REGACK
>> RX --> ACK
>> TX <-- POKE
>> RX --> PONG
>> Peer 'XXX' is now REACHABLE!
>> TX <-- ACK
>>
>> The different between both traces is the POKE PONG sequence.
>> In the libiax2/src/iax.c file is no code for the POKE request ?
>>
>> Any comment's ?
>> What is going wrong ?
>>
>> Is there anyone able to register a iaxclient to asterisk ?
>> ( iax2 show peers   --> Status OK )
>>
>> Regards
>>
>>     Stephan
>>
>>
>