And I think you are wrong about last \x00
Look at attached screenshot, I think you does not have field that is
highlighted "End of optional parameter" this must be last \x00 in
string to get correct part with ISUP.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
sorry
correct function is isup_update_destination
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
tel: (+38067) 403-62-54
2016-08-05 16:29 GMT+03:00 Sergey Basov :
> You are welcome.
>
>
> If you shure about last \x00 then you can try to edit
> modules/sipt/s
You are welcome.
If you shure about last \x00 then you can try to edit modules/sipt/ss7_parser.c
in function isup_update_bci_1
after strings
// pointer to fixed part (2)
offset++;
add next
// fixing Media requirements to speech 0x00 or 0x01 to 64k
tmp_buf[0] = 0x00;
tmp_buf[1] = 0x0A;
tmp_buf[2]
yes, that's x00 it's actually the only one well interpreted by
kamailio :)
thanks for the help in this issue Sergey
El vie, 05-08-2016 a las 15:01 +0300, Sergey Basov escribió:
> Hello.
>
> Most important, i think, is the las \x00 which is the flag end of ISUP
> message...
> Without it you can
Hello.
Most important, i think, is the las \x00 which is the flag end of ISUP
message...
Without it you cant generate correct ISUP part..
Look in wireshark. It will inform you about any error in ISUP.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
tel: (+3806
Hello
that would be great, despite not needing it now, it would be great,
there are 3 x00 in the isup i wanted to set, but 2 are from FCI and
optional FCI, and the third is for the called party, which can be
changed with sipt functions.
anycase, the FCI could be an issue in some scenarios, so an
Hello,
maybe the function append_body_part("...") can be extended with an extra
parameter where to specify the character to be replaced with 0x00 in the
first parameter.
Cheers,
Daniel
On 01/08/16 16:34, Sergey Basov wrote:
>
> Hello.
>
> Look more carefuly, its only first \x00 changes forward
Hello.
Look more carefuly, its only first \x00 changes forward call indicator. You
have a few more \x00...
You does not get full ISUP into INVITE...
As I have told earlier you can replace \x00 by \x01into kamailio script,
but you must rewrite it with \x00 later into sip-t module, but this
requir
Hello Sergey, Daniel
thanks a lot for the guidance.
i changed the x00 by x01 and it works now, i was seeing the ISUP
truncated but i thought it was related to the tshark XD
i will find out about the changes needed at sipt configuration, but just
in case, the things chaged by this only are the for
Hello,
I am not familiar with isup and no testbed around at this moment. That's
why I asked for backtrace from the coredump file, based on the
guidelines I did in my previous email.
Cheers,
Daniel
On 01/08/16 09:07, Sergey Basov wrote:
> Hello,
>
> try make dump packet after
> append_body_part(
Hello,
try make dump packet after
append_body_part("\x01\x12\x49\x00\x0a\x03\x02\x0a\x08\x84\x90\x33\x41\x72\x17\x00\x06\x0a\x08\x04\x13\x93\x70\x21\x73\x23\x10\x08\x01\x00\x00","application/isup;version=itu-t92+","signal;handling=optional");
before sipt_destination($rU, 31, 4);
when i have done
Hello,
would be good to get a core dump file and the backtrace from it in order
to see where it crashes.
For getting the coredump, try:
- stop kamailio
- do: ulimit -c unlimited
- start kamailio as root
- reproduce the issue
A corefile should be generated in / or working directory. Use g
12 matches
Mail list logo
