Results 1 to 5 of 5

Thread: Debugging ISDN signalling issues

  1. #1
    Join Date
    Jul 2008
    Posts
    268

    Default Debugging ISDN signalling issues

    Sometimes to help troubleshooting ISDN interoperability issues it is useful to collect ISDN signalling logs. To specifically enable layer 2/3 ISDN logging on Warp change/add the following in the '/etc/pika/pikagp_aoh.cfg' file on Warp:

    ...
    [logs]
    level=none
    size=4
    api=0x800C0000
    object.span=0xffffffff ;to log span actions
    object.board=0xffffffff ;to log board actions
    object.cstk=0x00303300 ;to log ISDN2 messages
    ...

    This change then requires Asterisk to be restarted.

    The resulting logs are typically found under '/var/log/pika/aoh' by default. (However their exact location is set by the 'PKH_LOGS_DIR' path variable in the '/etc/localenv' file and then located under a 'aoh' sub-directory.)

    The logs contain complete messaging which should help you or pika support determine the related signalling issue.

  2. #2
    fsinetworks Guest

    Default

    Hello,

    I followed your instructions and i have two log files :
    aoh_20110416_105530
    gp_20110416_105530
    but when i tried to open with vi, i have a message "gp_20110416_105530" Not a regular file.

    In fact, when i have an incoming call two bri channels ringing !!! and my telecom provider " France Telecom" say the problem is the Pika Warp !!

    warp*CLI>
    [Apr 16 11:05:58] NOTICE[6754]: chan_pika.c:4833 do_GP_event: GP group/channel 1/0: <-- PKX_EVENT_GROUP_INCOMING_CALL
    -- Executing [7800@from-numeris:1] NoOp("PIKA/digital/1", ""On est dans le context numeris"") in new stack
    -- Executing [7800@from-numeris:2] Dial("PIKA/digital/1", "SIP/101&SIP/106|20|tTwW") in new stack
    -- Called 101
    -- Called 106
    [Apr 16 11:05:58] NOTICE[6754]: chan_pika.c:4833 do_GP_event: GP group/channel 1/2: <-- PKX_EVENT_GROUP_INCOMING_CALL
    -- Executing [7800@from-numeris:1] NoOp("PIKA/digital/3", ""On est dans le context numeris"") in new stack
    -- Executing [7800@from-numeris:2] Dial("PIKA/digital/3", "SIP/101&SIP/106|20|tTwW") in new stack
    -- Called 101
    -- Called 106
    -- SIP/101-1031c630 is ringing
    -- SIP/101-1031c630 is ringing
    -- SIP/101-10319860 is ringing
    -- SIP/101-10319860 is ringing
    -- Got SIP response 486 "Busy Here" back from 192.168.1.233
    -- SIP/106-103091c0 is busy
    -- SIP/106-102e04a8 is ringing
    == Spawn extension (from-numeris, 7800, 2) exited non-zero on 'PIKA/digital/1'
    == Spawn extension (from-numeris, 7800, 2) exited non-zero on 'PIKA/digital/3'
    warp*CLI>
    Best Regards,
    Fabien

  3. #3
    Join Date
    Jul 2008
    Posts
    268

    Default

    aoh_xxxxxx and gp_xxxxxx are directories. There should be log files in them.
    Do you have a ring group configured?

  4. #4
    fsinetworks Guest

    Default

    Hello,

    I have not a ring group configured.
    I tried to connect one bri to the Pika warp asterisk and the other bri to an other bri PBX ( Diatonis 6 contact ).
    When i have an incoming call the two pbx ring.
    Apparently, we can not include in your forum some files.

    Best regards,
    Fabien

  5. #5

    Default

    The attachment of txt files should now be possible.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •