How To Configure VoIP survival with Broadsoft - Ingate

How To ConfigureVoIP SurvivalwithBroadsoft Remote SurvivalSeptember, 2009Ingate Systems Page: 1(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc

Table of Content1 Introduction .....................................................................................32 Network Setup ................................................................................33 Configuration ..................................................................................33.1 Status ...........................................................................................44 Log example ...................................................................................4Versions: Ingate Firewall/SIParator version 4.8BroadWorks version 16.0Revision History:Revision Date Author Comments0.1 2009-09-10 Janne Magnusson 1 st draftIngate Systems Page: 2(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc

1 IntroductionThe Ingate can be made to monitor SIP domains to ensure that theservers managing the domains really are reachable. If a SIP domainserver is unreachable, the Ingate will enter Survival mode, when itacts as a local registrar for the domain. This could be useful whenyou have a local office with an Ingate and all users register on aserver at the main office.When in Survival mode, the Ingate acts as a SIP registrar for thedomain. It can also redirect SIP calls to a PSTN gateway, if the calleelooks like a phone number (that is, if the URI user part containsnothing but digits, +, -, # and *).When the VoIP Survival feature is enabled the Ingate will also addan additional header in the SIP Register message causing the serverto provide additional information about the user, e.g. aliases orextensions for the user. This means that extension dialing worksbetween local users even though communication with the mainserver is lost.This document describes how VoIP Survival is configured with aBroadWorks server.2 Network SetupClients are located behind an Ingate Firewall or Ingate SIParator withthe Registrar function located outside of the Ingate, e.g. on a MainOffice or in a hosted solution.3 ConfigurationAll needed configuration is done on one pageIngate Systems Page: 3(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc

3.1 StatusStatus information. Notice the additional user information providedfrom Broadworks in the Survival Aliases column.4 Log exampleBelow follows a capture from a Registration with VoIP Survivalenabled.From UA to IngateREGISTER sip:as.iop1.broadworks.net SIP/2.0Ingate Systems Page: 4(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc

Via: SIP/2.0/UDP 10.100.0.71:2055;branch=z9hG4bK-0u0r5cn5j9qn;received=10.100.0.71;rport=2055From: "IngateUser2" ;tag=9q2qwrw6baTo: "IngateUser2" Call-ID: 3c2b7cb554c8-rzujpi0r4v0xCSeq: 868 REGISTERMax-Forwards: 70Contact: ;reg-id=1;q=1.0;+sip.instance="";audio;mobility="fixed";duplex="full";description="snom320";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"User-Agent: snom320/7.3.14Supported: gruuAllow-Events: dialogX-Real-IP: 10.100.0.71Expires: 3600Content-Length: 0From Ingate to the BroadWorks server (notice that Ingate added“Allow-Events: BroadWorksSubscriberData”)REGISTER sip:as.iop1.broadworks.net SIP/2.0Via: SIP/2.0/UDP 88.131.69.205:5060;branch=z9hG4bKbc30e2083fe7e35577463b3d0f9d9a06.0Via: SIP/2.0/UDP 88.131.69.205:2055;rport=2055;branch=z9hG4bK-0u0r5cn5j9qn.aMCEecZ+zSvcUntckVZYaA__From: "IngateUser2" ;tag=9q2qwrw6baTo: "IngateUser2" Call-ID: 3c2b7cb554c8-rzujpi0r4v0xCSeq: 868 REGISTERMax-Forwards: 69Contact: ;expires=3600;reg-id=1;q=1.0;+sip.instance="";audio;mobility="fixed";duplex="full";description="snom320";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"User-Agent: snom320/7.3.14Supported: gruuAllow-Events: dialog, BroadWorksSubscriberDataX-Real-IP: 10.100.0.71Expires: 3600Content-Length: 0From BroadWorks server to Ingate (notice Subscriber data fromBroadWorks)SIP/2.0 200 OKVia:SIP/2.0/UDP88.131.69.205:5060;branch=z9hG4bKbc30e2083fe7e35577463b3d0f9d9a06.0,SIP/2.0/UDP88.131.69.205:2055;branch=z9hG4bK-0u0r5cn5j9qn.aMCEecZ+zSvcUntckVZYaA__;rport=2055From:"IngateUser2";tag=9q2qwrw6baTo:"IngateUser2";tag=638037332-1248853483201Call-ID:3c2b7cb554c8-rzujpi0r4v0xCSeq:868 REGISTERContact:;q=1;expires=3599Allow-Events:call-info,line-seize,dialog,message-summary,as-feature-eventContent-Type:application/BroadsoftDocument+xmlContent-Length:303< subscriberData"version="1.0">2413332942IngateUser2@as.iop1.broadworks.net2942From Ingate to UASIP/2.0 200 OKVia: SIP/2.0/UDP 10.100.0.71:2055;rport=2055;branch=z9hG4bK-0u0r5cn5j9qn;received=10.100.0.71Ingate Systems Page: 5(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc

From:"IngateUser2";tag=9q2qwrw6baTo:"IngateUser2";tag=638037332-1248853483201Call-ID:3c2b7cb554c8-rzujpi0r4v0xCSeq:868 REGISTERContact: ;q=1;expires=3599Allow-Events:call-info,line-seize,dialog,message-summary,as-feature-eventContent-Length: 0Ingate Systems Page: 6(6)HowTo_Configure_VoIP_Survival_with_Broadsoft.doc