Troncal SIP "Notify" - "Bad Event"

Discussion in 'Elastix 2.x' started by Tato, Sep 29, 2010.

  1. Tato

    Joined:
    Sep 8, 2010
    Messages:
    14
    Likes Received:
    0
    Hola que tal, como les va.

    Quería hacerles una consulta. Tengo un troncal SIP y estoy viendo que mi proveedor (Crossfone Argentina) para mantener viva la conexión utiliza el comando NOTIFY y el cual mi Elastix responde "489 Bad event". No se si existe un parche o algo por el estilo. De todas maneras esto no me esta trayendo problemas, pero por las dudas consulto.
    Adjunto un sip Debug por ip. Primero mi central manda un keep alive, y después mi proveedor hace lo mismo


    REGISTER 13 headers, 0 lines
    Reliably Transmitting (NAT) to xxx.xxx.xxx.xxx:5060:
    REGISTER sip:xxxxxxxxx.xxxxxxxxx.com SIP/2.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK45e7e1f1;rport
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=as14fa7c6d
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>
    Call-ID: 67c3084f6a63b04b0187692b5f4eb4cc@127.0.0.1
    CSeq: 108 REGISTER
    User-Agent: Asterisk PBX
    Max-Forwards: 70
    Authorization: Digest username="xxx.xxx.xxx.xxx", realm="xxxxxxxxx.xxxxxxxxx.com", algorithm=MD5, uri="sip:xxxxxxxxx.xxxxxxxxx.com", nonce="630f3414-cbd9-11df-bd10-277fc2f1a0f3", response="f4c329dc336ef24ef83cfd774820b076", qop=auth, cnonce="23236b63", nc=00000002
    Expires: 120
    Contact: <sip:xxx.xxx.xxx.xxx@xxx.xxx.xxx.xxx>
    Event: registration
    Content-Length: 0


    ---
    PBX325617*CLI>
    <--- SIP read from xxx.xxx.xxx.xxx:5060 --->
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK45e7e1f1;rport=64719
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=as14fa7c6d
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=geg94jXv769HD
    Call-ID: 67c3084f6a63b04b0187692b5f4eb4cc@127.0.0.1
    CSeq: 108 REGISTER
    User-Agent: DINMAX CommCenter Proxy 1.1
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH
    Supported: timer, precondition, path, replaces
    WWW-Authenticate: Digest realm="xxxxxxxxx.xxxxxxxxx.com", nonce="0cfb8c98-cbda-11df-bd10-277fc2f1a0f3", stale="true", algorithm=MD5, qop="auth"
    Content-Length: 0


    <------------->
    --- (11 headers 0 lines) ---
    Responding to challenge, registration to domain/host name xxxxxxxxx.xxxxxxxxx.com
    REGISTER 13 headers, 0 lines
    Reliably Transmitting (NAT) to xxx.xxx.xxx.xxx:5060:
    REGISTER sip:xxxxxxxxx.xxxxxxxxx.com SIP/2.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK7e2b2fb1;rport
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=as26169d00
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>
    Call-ID: 67c3084f6a63b04b0187692b5f4eb4cc@127.0.0.1
    CSeq: 109 REGISTER
    User-Agent: Asterisk PBX
    Max-Forwards: 70
    Authorization: Digest username="xxx.xxx.xxx.xxx", realm="xxxxxxxxx.xxxxxxxxx.com", algorithm=MD5, uri="sip:xxxxxxxxx.xxxxxxxxx.com", nonce="0cfb8c98-cbda-11df-bd10-277fc2f1a0f3", response="888093f87c663085a305dc9119e3c9f7", qop=auth, cnonce="57f30ee8", nc=00000001
    Expires: 120
    Contact: <sip:xxx.xxx.xxx.xxx@xxx.xxx.xxx.xxx>
    Event: registration
    Content-Length: 0


    ---
    PBX325617*CLI>
    <--- SIP read from xxx.xxx.xxx.xxx:5060 --->
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK7e2b2fb1;rport=64719
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=as26169d00
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=j02t88y31rpQm
    Call-ID: 67c3084f6a63b04b0187692b5f4eb4cc@127.0.0.1
    CSeq: 109 REGISTER
    Contact: <sip:xxx.xxx.xxx.xxx@xxx.xxx.xxx.xxx>;expires=300
    Date: Wed, 29 Sep 2010 14:58:42 GMT
    User-Agent: DINMAX CommCenter Proxy 1.1
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH
    Supported: timer, precondition, path, replaces
    Content-Length: 0


    <------------->
    --- (12 headers 0 lines) ---
    Scheduling destruction of SIP dialog '67c3084f6a63b04b0187692b5f4eb4cc@127.0.0.1' in 32000 ms (Method: REGISTER)
    PBX325617*CLI>
    <--- SIP read from xxx.xxx.xxx.xxx:5060 --->
    NOTIFY sip:xxx.xxx.xxx.xxx@xxx.xxx.xxx.xxx:64719;received=xxx.xxx.xxx.xxx:64719;fs_nat=yes SIP/2.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;rport;branch=z9hG4bK8e133eD4v4Zvj
    Max-Forwards: 70
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=mjNccZ0ava3vB
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>
    Call-ID: e46b16f2-467c-122e-878b-ffc6ac3266ef
    CSeq: 2550097 NOTIFY
    Contact: <sip:mod_sofia@xxx.xxx.xxx.xxx:5060>
    User-Agent: DINMAX CommCenter Proxy 1.1
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH
    Supported: timer, precondition, path, replaces
    Event: message-summary
    Allow-Events: talk, presence, dialog, call-info, sla, include-session-description, presence.winfo, message-summary, refer
    Subscription-State: terminated;reason=timeout
    Content-Type: application/simple-message-summary
    Content-Length: 89

    Messages-Waiting: no
    Message-Account: sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com


    <------------->
    --- (16 headers 3 lines) ---
    Sending to xxx.xxx.xxx.xxx : 5060 (NAT)

    <--- Transmitting (NAT) to xxx.xxx.xxx.xxx:5060 --->
    SIP/2.0 489 Bad event
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bK8e133eD4v4Zvj;received=xxx.xxx.xxx.xxx;rport=5060
    From: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=mjNccZ0ava3vB
    To: <sip:xxx.xxx.xxx.xxx@xxxxxxxxx.xxxxxxxxx.com>;tag=as0681d2b9
    Call-ID: e46b16f2-467c-122e-878b-ffc6ac3266ef
    CSeq: 2550097 NOTIFY
    User-Agent: Asterisk PBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
    Supported: replaces
    Content-Length: 0


    Desde ya muchas gracias!
     
  2. netaires

    Joined:
    Apr 13, 2010
    Messages:
    218
    Likes Received:
    1
    Hola. A ver si te sirve esta ayuda, ver de registrarte una troncal en CamundaNet.
    Probar configurarla en tu Elastix a ver si hace lo mismo, como para sacar la duda de donde viene el problema.
     

Share This Page