2 Replies Latest reply on Oct 6, 2014 9:02 AM by geo

    Adtran 908 SIP Options Ping

    xtropx New Member

      I am getting a SIP Options Request ping from our Metaswitch SBC which will determine if the trunk is "active" and ready to place calls.

       

      Now I cannot seem to get this to happen. I have followed advice in this thread: SIP OPTIONS request gets answered by a 501 Not Implemented and then I can see the options pings are responding OK

       

      08:57:56.030 SIP.STACK MSG Rx: UDP src=209.81.107.134:5060 dst=10.4.49.202:5060
      08:57:56.031 SIP.STACK MSG     OPTIONS sip:metaswitch@10.4.49.202:5060;transport=udp SIP/2.0
      08:57:56.032 SIP.STACK MSG     Via: SIP/2.0/UDP 209.81.107.134:5060;rport;branch=z9hG4bK+34e265e13f5bbb15918f8814b8c0092c1+sip+1+a706d2db
      08:57:56.032 SIP.STACK MSG     From: <sip:metaswitch@172.16.1.2:5060;transport=udp>;tag=209.81.107.134+1+f6418d03+9c01e726
      08:57:56.033 SIP.STACK MSG     Content-Length: 0
      08:57:56.033 SIP.STACK MSG     Supported: resource-priority, 100rel
      08:57:56.033 SIP.STACK MSG     To: <sip:metaswitch@10.4.49.202>
      08:57:56.034 SIP.STACK MSG     Contact: <sip:3dee133f51b1dfbd6aa36c38415b2e02@209.81.107.134:5060>
      08:57:56.034 SIP.STACK MSG     Allow-Events: message-summary, refer, dialog, line-seize, presence, call-info, as-feature-event
      08:57:56.035 SIP.STACK MSG     Max-Forwards: 69
      08:57:56.035 SIP.STACK MSG     Call-ID: 0gQAAC8WAAACBAAALxYAAFNYUtnhsdSutS87KbPvFwdi0PnuQSREbiVfpUahpZ5E@209.81.107.134
      08:57:56.036 SIP.STACK MSG     CSeq: 73959982 OPTIONS
      08:57:56.036 SIP.STACK MSG     Organization:
      08:57:56.037 SIP.STACK MSG     Accept: application/sdp, application/dtmf-relay
      08:57:56.037 SIP.STACK MSG
      08:57:56.042 SIP.STACK MSG Tx: UDP src=10.4.49.202:5060 dst=209.81.107.134:5060
      08:57:56.043 SIP.STACK MSG     SIP/2.0 200 OK
      08:57:56.043 SIP.STACK MSG     From: <sip:metaswitch@172.16.1.2:5060;transport=udp>;tag=209.81.107.134+1+f6418d03+9c01e726
      08:57:56.044 SIP.STACK MSG     To: <sip:metaswitch@10.4.49.202>;tag=25792a8-7f000001-13c4-1085-8cfa9296-1085
      08:57:56.044 SIP.STACK MSG     Call-ID: 0gQAAC8WAAACBAAALxYAAFNYUtnhsdSutS87KbPvFwdi0PnuQSREbiVfpUahpZ5E@209.81.107.134
      08:57:56.045 SIP.STACK MSG     CSeq: 73959982 OPTIONS
      08:57:56.045 SIP.STACK MSG     Via: SIP/2.0/UDP 209.81.107.134:5060;rport=5060;branch=z9hG4bK+34e265e13f5bbb15918f8814b8c0092c1+sip+1+a706d2db
      08:57:56.046 SIP.STACK MSG     Supported: 100rel,replaces
      08:57:56.046 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
      08:57:56.047 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A4.11.00.E
      08:57:56.047 SIP.STACK MSG     Content-Length: 0

       

      Metaswitch still says I am down: