Home

Avaya Bell Canada SIP Trunking Service with Business Communication Manager 450 Application Note

1. ZE Status Gateway is running a m L_C 0 L__M 0 __m 17 __W 59 TD Reviewed Solution amp Interoperability Test Lab Application Notes 14 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 3 3 Administer Public Port The Public Port is used to receive the SIP traffic from the service provider In the compliance testing it was set to 5060 as the default value that was preferred by Bell Canada To configure the Public Port select Configuration gt Resources gt IP Trunks gt SIP Trunking Under Public tab select Settings then configure the Provisioned Public Port to 5060 as shown in the screenshot below FW Avaya Business Element Manager 10 10 07 3 File Edit View Network Session Tools Help dra K cut My Copy MB Paste web Page q validate Device Sj Disconnect Refresh Mf Auto refrest SIP Trunking a Global Settings Media Parameters Routing Table Settings Accounts ITSP Templates Public Network Discovered Public Address 0 0 0 0 Address Discovery Flag Provisioned Public Address Done L Cat M t m17t weg TD Reviewed Solution amp Interoperability Test Lab Application Notes 15 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 3 4 Create a Public Account To create a Public Account click Accounts tab then click Add button to add a public account for Bel
2. Hospitality Hunt Groups Cal Detail Recording Call Recording Data Services Applications D Intercom Keys ControlSet FFirstDisplay Auto Called ID Capabilities SWCA Cal Group Preferences J ip Terminal Detais Button Programming Table Button Programming User Speed Dial Language English Call log options Mo one answered Dialing options Standard dial m Log space 0 Contrast 4 e Available log space 3000 Ring type 1 sl Reset Call Log Password Distinct rings in use Pattern 2 Hotline Hotline type None Aux ringer Business name Business name 1 Long name Send long name TD Reviewed SPOC 3 15 2013 Include ACKed alarms Solution amp Interoperability Test Lab Application Notes 31 of 45 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 8 Administer Outgoing Call Calling Party Number Delivery For outgoing calls the Calling Party Number will be derived from the Pub OLI setting of an active DN It will be presented as the URI User of the From header To configure the Pub OLI select Configuration gt Telephony gt Sets gt Active Sets Under Line Access tab define Pub OLI for an active DN e g 22264 as 416XXX1398 as shown in the screenshot below A Ava a Bu siness Ele S i nt Mana Kei r 10 10 97 34 File Edit View Network Session Tools Help Kr Ex
3. Verify that endpoints at the enterprise site can place calls to PSTN and that the call remains active for more than 35 seconds This time period is included to verify that proper routing of the SIP messaging has satisfied SIP protocol timers Verify that endpoints at the enterprise site can receive calls from PSTN and that the call can remain active for more than 35 seconds Verify that the user on PSTN can end an active call by hanging up Verify that an endpoint at the enterprise site can end an active call by hanging up 6 2 Protocol Traces The following SIP message headers are inspected using sniffer traces Request URI Verify the request number and the SIP domain From Verify the display name and display number To Verify the display name and display number P Asserted Identity Verify the display name and display number Privacy Verify the privacy masking with user id Diversion Verify the DID number Authorization Verify the Digest Authentication implementation The following attributes in SIP message body are inspected using sniffer traces Connection Information c line Verify the IP addresses of near and far endpoints Time Description t line Verify the session timeout value of near and far endpoints Media Description m line Verify the audio port codec DTMF event description Media Attribute a line Verify the specific audio port codec ptime send receive abilities DTMF event and fax attributes
4. Applica 22393 Templates Application 22394 Ge Application 22395 22396 22397 BCU 22398 22399 b Done L Col molo mOl wt V Include ACKed alarms 5 5 10 Administer Incoming Call Target Lines For incoming calls BCM450 uses Target Lines to terminate the calls that match the configured Pub Received numbers The Target Line is assigned as a key on the phone The maximum available Target Line is ruled by the system license To add a Target Line to a a phone select Configuration gt Telephony gt Sets gt Active Sets Under the Line Access tab select an active DN e g 22264 then go to the Line Assignment and click Add not shown In the Add Line Assignment dialog enter the available Target Line e g 964 The sample configuration shows active DN 22264 was configured with Target Line 964 to receive incoming call to DID number 416XXX1398 It is shown in the screenshot below e Target Line 964 e Appearance Type Appr amp Ring This allows the Target Line to display as a key on the phone and it will ring per incoming call that matches the configured Priv Received or Pub Received e Appearance The Target Line will be displayed as 1 particular key on the phone Increase the Apparance if more than 1 key are needed e Caller IP Set Checked This enables the Calling Party Name and Number to display on the phone e Vmsg Set Checked if the phone has voice mail enabled on the integrated CallPilot otherwise leave
5. To configure the Basic settings select Basic tab of the account BellCanada created above In the compliance testing the Basic settings were configured with following values e SIP Domain o Remote The service provider public SIP domain e g sipxxxxxxxx bell ca populated from the Public Account as shown in Section 5 3 4 o Local Enter the enterprise public SIP domain e g cust2xxxx xxxx bell ca This SIP domain is obtained through Bell Canada e Proxy o Address Enter the SIP domain that matches the entry defined next in Outbound Proxy Table In the compliance testing the SIP domain sipxxxxxxxx bell ca was added with the Proxy Address is the IP address of Bell Canada Central Office e g 220 20 237 201 o Port Enter the port that Bell Canada is expecting to receive the SIP signaling from BCM450 In the compliance testing Bell Canada preferred to port 5060 o Transport UDP This is the default value on BCM450 and not configurable e Registrar Leave these fields blank as default Bell Canada does not require Registration on the SIP Trunk e Outbound Proxy Table TD Reviewed Solution amp Interoperability Test Lab Application Notes 17 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM o Domain Enter the service provider public SIP domain e g sipxxxxxxxx bell ca o IP Address Enter the IP address of Bell Canada Central Office e g 220 20 237 201 o Port Enter the port 5060 that Bell Canada is expecting to receiv
6. 20 2357 520i Ss SOGOR Iie x nt corr id 345a1170 870a6122 13c4 55013 19b8 6 233c7e 19b8 Contact lt sip 416XXX1398 10 10 97 34 5060 transport udp gt Authorization Digest username avaya realm Sipxxxxxxxx bell ca nonce BroadWorksxh8hpmutwT11z2y4BWw u ri sip 1613XXX5279 sipxxxxxxxx bell ca transport udp response 14a9e80efcl58f4dce a494848675b059 algorithm MD5 cnonce 6479ec gop auth nc 00000001 Session Expires 90 Allow INVITE INFO ACK OPTIONS CANCEL BYE NOTIFY PRACK UPDATE REFER Content Type application sdp Content Length 263 v 0 O 15350677620 ISSOCTTEZO IN TRA TO LO 93A g IN IP4 10 10 97 34 0 audio 30142 RTP AVP 0 18 101 111 ENG EPA OPO Teo fmtp 18 annexb no rtpmap 101 telephone event 8000 Emtee LOL 0 15 rtpmap 111 X nt inforeq 8000 sendrecv E m a a a a a TD Reviewed Solution amp Interoperability Test Lab Application Notes 40 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM e Incoming 2000K response from Bell Canada SIP 2 0 ZOO Ox From BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt tag 34414cd8 870a6122 13c4 55013 19b8 44869384 19b8 To lt sip 1613XXX5279 sipxxxxxxxx bell ca gt tag SDdsnqe99 1312326424 1350676031266 Call ID 345a1170 870a6122 13c4 55013 19b8 6 233c7e 19b8 Seqy 2 INVETE Via SIP 2 0 UDP 10 10 97 34 5060 branch z9hG4bK 19b8 6479ea 1208
7. Calling Party Number In this testing the Calling Party Number is set on each phone individually therefore it is unnecessary to define the Public network code TD Reviewed Solution amp Interoperability Test Lab Application Notes 26 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 4 Administer Outgoing Call Routing A route was created for outgoing calls to Bell Canada To create a route select Configuration gt Telephony gt Dialing Plan gt Routing Under the Routes tab click Add to create a new route not shown In the compliance testing route 001 was added to use pool BlocA as show in the screenshot below e Route 001 o Use Pool BlocA o DN Type Public Unknown D Avaya Business Element Manager 1010 97 34 o S I SCH File Edit View Network Session Tools Help KE Exit A Cut os Copy SS Paste Web Page wf Validate Device YG Disconnect E Refresh ZS Auto refresh Task Navigation Panel Dialing Plan Routing Configuration Administration b Telephony Fetes Destination Codes Second Dial Tone i Global Settings Routes Sets d Lines Loops l 1 gt Scheduled Service Public Unknown N A Diali i 00 Private Dialing Plan y General 003 National DNs National Public Network Public Unknown Private Networ ine Poo Routing Route External Number Use Pool Service Type L Co Mol mp wn 7 Include ACKe
8. Use a network sniffing tool e g Wireshark to monitor the SIP signaling between the enterprise and Bell Canada The sniffer traces are captured at the public interface of BCM450 TD Reviewed Solution amp Interoperability Test Lab Application Notes 36 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM Following screenshots show an example incoming call from Bell Canada to the enterprise Incoming INVITE request from Bell Canada INVITE sip 416XXX1398 cust2xxxx xxxx bell ca transport udp SIP 2 0 Via SIP 2 0 UDP 220 20 237 201 5060 branch z 9hG4bKi0m9ki3038alo0186n0c1 1 From lt sip 1613XXX5258 sipxxxxxxxx bell ca user phone gt tag SDocfbb01 453254403 LSHOG TT LLST Vala To Bell Demol2345 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt Call ID SDocfbb01 09eee563259466f2de0a5057d0 97d6 a0n8330 CSeq 1028992414 INVITE Contact lt sip 1613XXX5258 220 20 237 201 5060 transport udp gt Supported 100rel Allow ACK BYE CANCEL INFO INVITE OPTIONS PRACK REFER NOTIFY UPDATE Accept multipart mixed application media_control xml application sdp Max Forwards 18 Content Type application sdp Content Length 207 v 0 o BroadWorks 6273513 1 IN IP4 220 20 237 201 ges c IN IP4 220 20 237 201 t 0 0 m audio 20396 RTP AVP 0 18 101 a rtpmap 101 telephone event 8000 a fmtp 101 0 15 a ptime 20 a fmtp 18 annexb no TD Reviewed Solution amp Interopera
9. resolution at this time This issue has low user impact it is listed here simply as an observation 4 The BCM450 station off net transfers an incoming outgoing from to PSTN_1 call back to PSTN_2 the Calling Party Number is not updated Even the call was successfully transferred but BCM450 did not send subsequent INVITE or UPDATE to Bell Canada on both call legs with the Contact or P Asserted Identity headers containing the Calling Party Number of the true connected PTSN parties Both PSTN parties still displayed the Pub OLT of the BCM450 station This is a known behavior of BCM450 with no available resolution at this time This issue has low user impact it is listed here simply as an observation 5 The 3 way conference call which was initiated by the BCM450 station drops if all local stations leave the conference This is a known behavior of BCM450 with no available resolution at this time This issue has low user impact it is listed here simply as an observation 6 The Find Me Follow Me FMFM users display the Pub OLI of the Virtual Application DN instead of displaying the original Calling Party Number of PSTN party Bell Canada examined the Calling Party Number of outgoing twinned calls so the Pub OLP of the Virtual Application DN has to be set to one of the subscribed DID numbers Otherwise outgoing calls to FMFM users will be rejected This workaround results the original Calling Party Number of PSTN p
10. 416 6 digit extension File Edit View Network Session Tools Help P Ext A Cut Ba Copy Paste web Page H Validate Device YG Disconnect E Refresh A Dialing Plan Routing e Routes Destination Codes second Dial Tone C A DialingPlan General DNs Public Netwo Private Netw ing Po MI i Routing Ring Groups md Call Security WI r L Col Mo mol wn Include 4CKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 28 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 6 Administer Outgoing Call SIP Trunk Routing Table As the Destination Codes are defined to use Line Pool BlocA that contains VoIP Lines which may be shared between H 323 and SIP Trunks In order to route outgoing calls with the defined Destination Codes over the SIP Trunk the appropriate routes need to be defined under the Routing Table for SIP Trunk To create an entry in the Routing Table for the SIP Trunk select Configuration gt Resources gt IP Trunk gt SIP Trunking Under the Public tab select Routing Table and then click Add not shown In the compliance testing multiple routes e g 0 1 411 and 416 were created for Public Account BellCanada see Section 5 3 4 as shown in the screenshot below Avaya Business Element Manager 10 10 97 34 File Edit View Network Session Tools cil g Exit i X cut Ba Copy DI Paste Web P
11. Rights Reserved BCSIPTrkBCM Following screenshots show an example outgoing call from the enterprise to Bell Canada e Outgoing INVITE request from the enterprise INVITE sip 1613XXX5279 sipxxxxxxxx bell ca transport udp SIP 2 0 From BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt tag 34414cd8 870a6122 13c4 55013 19b8 44869384 19b8 To lt sip 1613XXX5279 sipxxxxxxxx bell ca gt Call ID 345a1170 870a6122 13c4 55013 19b8 6 233c7e 19b8 CSeq 1 INVITE Via SIP 2 0 UDP 10 10 97 34 5060 branch z 9hG4bK 19b8 6479a3 cld6 dbd Max Forwards 70 Supported sipvc x nortel sipvc 100rel replaces timer User Agent Nortel Networks BCM VoIP Gateway release 46 version 46 51 0 33 P Asserted Identity BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt Diversion lt sip 4167751881 cust2xxxx xxxx bell ca gt reason unconditional ROUESS SSos 220 20 7257 ee x nt corr id 345a1170 870a6122 13c4 55013 19b8 6 233c7e 19b8 Contact lt sip 416XXX1398 10 10 97 34 5060 transport udp gt Session Expires 90 Allow INVITE INFO ACK OPTIONS CANCEL BYE NOTIFY PRACK UPDATE Content Type application sdp Content Length 263 v 0 1350677620 SOGI TEZO IEN m24 MO LEE el LO LO Oy SA udio 30142 RTP AVP 0 18 101 111 OSLO 97 4 34 annexb no 101 telephone event 8000 RER 11 X nt inforeg 8000 sendrecv e Incoming 401 challenge to request the Digest Authenticatio
12. System A rk D Au Administrator Access BEE able ai IP Sets Enabled II Enable Deconfigure Configure E Details for Module Internal IP Sets Dial Up Interfaces E Telephony IP Terminal Global Settings f 1P Terminal Details Migrate Sets to IPO D Data Services 1 1 Applications Enable registration V Default codec G 711 uLaw Y Enable global registration password V Default jitter buffer Auto Global password eeseseeeeg G 729 payload size ms 20 Auto assign DNs 7 Play DTMF tone V G 711 payload size ms 20 x Advertisement Logo AVAYA BCM 450 Support Remote Worker 4 w r Done CO MO mn wn 7 Include ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 23 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 Administer Dialing Plan This section shows how to configure BCM450 VoIP Lines for outgoing calls over the SIP Trunk to Bell Canada For incoming calls BCM450 uses Target Lines for call termination or redirection 5 5 1 Associate Line Pool to VoIP Lines On BCM450 the VoIP Lines which are the resources of the SIP Trunk are assigned to a Line Pool which can be used to for outgoing call routing To associate a Line Pool to VoIP Lines select Configuration gt Telephony gt Lines gt Active VoIP Lines Under the Line Type of each VoIP Line select the pool name Poo
13. and the system license TD Reviewed Solution amp Interoperability Test Lab Application Notes 11 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 2 2 Administer Media Gateways Enable Echo cancellation on the Media Gateways by selecting Configuration gt Resources gt Media Gateways then select Enabled w NLP as shown in the following screenshot EY Avaya Business Element Mana ger 10 10 97 3 File Edit View Network Session Tools Help Ei X cut Ma Copy Paste Web Page of Validate Device YG dsc Echo cancellation Enabled w NLP w T 38 UDP redundancy 2 5 2 3 Administer Port Ranges To display the Port Ranges select Configuration gt Resources gt Port Ranges The default Port Ranges for the RTP traffic are shown in the following screenshot FW Avaya Business Element Manager 10 10 97 2 File Edit View Network Session Tools Help drai cut Wy Copy MB Paste web Page vd Validate Device Y Disconnect 20249 Ei Dial Up Interfaces _ Elke a Wi gt Done L_C 0 L__M 0 L___m 17 __W 60 7 Indude ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 12 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 3 Administer the SIP Trunk This section describes the steps for configuring the SIP Trunk on BCM450 connecting to Bell Canada 5 3 1 General IP Trunk settings The system se
14. small businesses to large enterprises Bell Canada SIP Trunking Service provides a flexible cost saving alternative to traditional hardwired telephony trunks All of the test cases have been executed Despite the number of observations seen during testing as noted in Section 2 2 the test results met the objectives outlined in Section 2 1 Bell Canada SIP Trunking Service is considered compliant with Avaya Business Communication Manager 450 Release 6 0 TD Reviewed Solution amp Interoperability Test Lab Application Notes 43 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 8 References This section references the documentation relevant to these Application Notes Additional Avaya product documentation is available at http support avaya com 1 Configuration Telephony Avaya Business Communication Manager Release 6 0 Document Number NN40170 502 Revision 03 01 May 2010 2 Planning and Engineering Avaya Business Communication Manager Release 6 0 Document Number NN40170 200 Revision 02 01 May 2010 3 CallPilot Reference Guide Avaya Business Communication Manager Release 6 0 Document Number NN40170 100 Revision 02 01 May 2010 4 RFC 3261 SIP Session Initiation Protocol http www ietf org 5 RFC 2833 RTP Payload for DTMF Digits Telephony Tones and Telephony Signals http www ietf org 44 of 45 TD Reviewed Solution amp Interoperability Test Lab Application Notes BCSIPT
15. 00 01 34 Use BCM450 Monitor to monitor RTPs The following screenshot shows 2 external RTP streams connecting to Bell Canada and 2 internal RTP streams connecting to local phones In the compliance testing BCM450 was configured to relay the media using G 711 codec File Statistics Help BCM Info Media Card Voice Ports IP Devices RTP Sessions UIP Line Monitor Usage Indicators r Local IP Endpoint RTP Session Details IP to IP d 10 97 34 30016 lt gt 4 SIP Trunk BellCanada 1 H 237 201 20008 G 711 2 fpp SMALL jb 0 RFC2833 TDM to IP 10 97 34 30022 lt gt SIP Trunk BellCanada 8 H 237 201 20010 G 711 2 fp SMALL jb 0 RFC283 TDM to TDM Set 22263 10 33 5 13 51020 lt gt M 10 97 34 30020 G 711u 2 fpp SMALL jb EEN Set 22264 10 33 5 10 51022 lt gt M 10 97 34 30018 G 711u 2 fpp SMALL jb Local to Remote IP Endpoint IP to IP m TDM to IP Ke Est bandwidth 697 6 kbps Remote IP Endpoints IP to IP 0 Est bandwidth 0 bps Media Gateways Active on call 0 of 2 TD Reviewed Solution amp Interoperability Test Lab Application Notes 42 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 7 Conclusion These Application Notes describe the configuration necessary to connect Avaya Business Communication Manager 450 Release 6 0 to Bell Canada SIP Trunking Service Bell Canada SIP Trunking Service is a SIP based Voice over IP solution for customers ranging from
16. AVAYA Avaya Solution amp Interoperability Test Lab Application Notes for Bell Canada SIP Trunking Service with Avaya Business Communication Manager 450 Release 6 0 Issue 1 0 Abstract These Application Notes describe the steps to configure Session Initiation Protocol SIP Trunking between Bell Canada SIP Trunking Service and an Avaya SIP enabled enterprise solution The Avaya solution consists of Avaya Business Communication Manager 450 Release 6 0 and various Avaya endpoints Bell Canada SIP Trunking Service provides PSTN access via a SIP trunk between the enterprise and Bell Canada network as an alternative to traditional PSTN trunks such as analog and or ISDN PRI This approach generally results in lower cost for the enterprise Bell Canada is a member of the Avaya DevConnect Service Provider Program Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab TD Reviewed Solution amp Interoperability Test Lab Application Notes 1 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM Table of Contents 1 Introductloneassc ccs Laken sine pana eae dag NEES aint Minnis 2 General Test Approach and Test Hesults eese eetntesrnetrnstrnsttnstnsrusstnssrnnsrnnsrnnsrnnsrnnnnnnt 2 1 Interoperability Compliance Testimg tetr tssrnsstnsn
17. E164 international dialing Min SE Enable SDP OPTIONS query Allow REFER Active call limit 0 Support Replaces Enable Connected Identity v Standard SIP Caps Exchange V ITSP association method To header local domain match e Outbound Called characters to absorb 0 e Inbound Called prefix to prepend Authentication realm TD Reviewed Solution amp Interoperability Test Lab Application Notes 19 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM Note e The other options were left as blank as default e The ITSP association method is set to match the local SIP domain of the To header as defined as cust2xxxx xxxx bell ca in Section 5 3 5 TD Reviewed Solution amp Interoperability Test Lab Application Notes 20 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 3 7 User Account settings Under the User Account settings the credential for Digest Authentication will be defined To change the User Account settings select User Account BellCanada then click Modify button as shown in the screenshot below SIP Username Bell Canada Mot registered In the Modify account dialog enter the User Credentials for Digest Authentication as shown in the screenshot below EQ Modify account Description Domain siptrunking bell ca Account identity Parent account User Credentials avaya avaya Seeeeeeeeeeeeece Realm Mes
18. G 711MU codec DTMF tone transmission as out of band RTP events as per RFC 2833 Voicemail navigation for incoming and outgoing calls CallPilot voicemail hosted on BCM450 User features such as hold and resume call waiting call park transfer forward and conference Off net call transfer using subsequent INVITE method Off net call forward using Diversion method Find Me Follow Me FMFM twining to incoming calls to cellular Meet me conferencing hosted on BCM450 Response to OPTIONS heartbeat Response to incomplete call attempts and trunk errors Session Timers implementation Items are not supported by Bell Canada on the test environment or not tested as part of the compliance testing are listed as following Inbound toll free and outgoing emergency calls E911 are supported but were not tested as part of the compliance testing because Bell Canada has not provided the necessary configuration G 729 codec is not supported Fax over IP with T 38 codec is not supported Off net calls transfer using REFER method is not supported Off net call forward using History Info method is not supported 2 2 Test Results Interoperability testing of Bell Canada with the Avaya SIP enabled enterprise solution was successfully completed with the exception of the observations limitations described below 1 The BCM450 station resumes a held outgoing PSTN call causes the Calling Party Number to change After retrieving the held call t
19. SIPTrkBCM 5 2 Administer Resources This section describes how to configure Application Resource Media Gateway and Port Ranges that will be used to administer the SIP Trunk 5 2 1 Administer Application Resources To display the Application Resources select Configuration gt Resources gt Application Resources Verify the Application Resources for the SIP Trunks by selecting SIP Trunks then click Modify button as shown in the following screenshot D Avaya Business Element Manager 10 10 97 34 File Edit View Network Session Tools Se dra K cut Ea Copy MB Paste web Page d Validate Device disconnect Sy Refresh MH Auto refresh ease este Don Resources Configuration Administration a Welcome Total Resources Reserved Resources E Spem Signalling channels Signalling channels 3 Administrator Access Reso VDI channels VDI channels popicaton Resources Media channels Media channels Port ani DSP resources 180 DSP resources 9 Telephony Resources e B IP Trunks Application Bees Reservations Dial Up Interfaces Application Minimum i i System Max Telephony ER e Data Services Applications ay en KE L 0 L__M 0 L_m 17 L__W 60 V Indude ACKed alarms A new dialog appears with title Modify Resource Application Reservations verify the maximum Application Resources for the SIP Trunks were allocated The available Application Resources are based on the system capacity
20. Services Applications 2 OR Voice Messaging cc H Music IVR X um t LAN CTE na a H E 4 Done L Cot Molom w V Include ACKed alarms When making an FMFM call to cellular extension BCM450 will use the Pub OLI assigned to the Application DN as the Calling Party Number It will be included as the URI User of the From header In the compliance testing Bell Canada examined the URI User of the From header for call authentication purpose it only grants access for the call if the URI User is one of the assigned DID number otherwise outgoing calls will be rejected Thus the Pub OLI of the appropriate Application DNs has to be set to a typical value e g 416XXX1399 which is one of the assigned DID numbers However this implementation is limited as per the observation 6 in Section 2 2 the FMFM users will display the Pub OLI 416XXX1399 instead of the original PSTN caller TD Reviewed Solution amp Interoperability Test Lab Application Notes 33 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM To set the Pub OLI for a DN refer to Section 5 5 8 The following screenshot shows the Application DN range 22392 22399 with the Pub OLI was set to 416XXX1399 D Avaya Business Element Manager 10 10 97 34 Co 1 fecal File Edit View Network Session Tools Help K Eat A Cut a Copy Paste Web Page H validate Device YG Disconnect Refresh f pplication 22392
21. age H Validate Device Disconnect SIP Trunking Private Global Settings Media Parameters Settings Accounts ITSP Templates A Name Destination Digits Account Dial Up Interface S A Telephony E Global Seling 4 Hi p F Done L Col Mo mp wn Include 4CKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 29 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 7 Administer Outgoing Call Calling Party Name Delivery This section shows how to configure Calling Party Name delivery over the SIP Trunk For example when an active DN e g 22264 makes an outgoing call the display name in the From header will be constructed using the Business Name and the phone Name configured as following To define the Businese Name select Configuration gt Telephony gt Global Settings gt Feature Settings Then define the Business Names Entry 1 as BCM450 as shown in the screenshot below Avaya Business Element Manager 10 10 97 34 1 lets File Edit View Network Session Tools Help A Ext X cut Ma copy Paste web Page H Validate Device YG Disconnect E Refresh ZE Auto refresh Task ee Panel Configuration Administration Feature Settings Business Names 1 39 BCM450 2 4 Ge m Done L Co M nL mp wn F Include ACked alarms To define the phone Name select Configuration gt Tele
22. arty will not be displayed on the FMFM users The FMFM users will display the Pub OLP of the Virtual Application DN 7 The off net call forward unconditional or busy scenarios fail if the forwarded PSTN party takes longer than 8 seconds to respond The issue has been seen on the cellular PSTN phone BCM450 relies on the respond time of the cellular PSTN phone on the ae leg to transmit the ringback back to the original calling PSTN party on the 1 leg If the respond time is greater than 8 seconds Bell Canada terminates the call with a CANCEL request on the Ist call leg This fails the scenarios The issue does not happen if the cellular PSTN phone in good wireless coverage that can significantly reduce the respond time under 8 seconds limit The same call scenarios are successful on the regular PSTN phone instead of the cellular PSTN party Bell Canada is recommended to increase the Session Provisioning Timer to correct the issue This is acknowledged as a known TD Reviewed Solution amp Interoperability Test Lab Application Notes 5 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM behavior of Bell Canada SIP Trunking Service with no resolution available at this time it is listed here as a limitation 2 3 Support For technical support on the Avaya products described in these Application Notes visit http support avaya com For technical support on Bell Canada SIP Trunking Service contact Bell Canada at htt
23. as shown in the following screenshot D Avaya Business Element Manager Network Elements 10 10 97 34 Lal 23 File Edit View Network Session Tools Help T Exit A Cut sy Copy GR Paste Web Page wf Validate Device Kc Connect J gt lt Delete Be New Folder Element Navigation Panel Connection Information IP Address 10 10 97 34 User ID nnadmin Password Jeeeeeesecccce Inventory Information System Name BCM450 System Description BCM450 System Software Version 10 0 2 14 236 Network Elements After the connection has been established click OK in the Confirm dialog not shown TD Reviewed Solution amp Interoperability Test Lab Application Notes 9 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM The screenshot below shows the Avaya Business Element Manager has been successfully logged on A usir clement nager 10 14 37 34 File Edit View Network Session Tools Help op ext AS Cut Ha Copy E Paste Web Page of Validate Device YG Disconnect SN Refresh E Auto efresh WARNING Your telset password must be changed WARNING The following account passwords must be changed Numeric ID 738662 User ID n Last successful login V Indude ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 10 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BC
24. bility Test Lab Application Notes 37 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM e 2000K response from the enterprise EE 0K From lt sip 1613XXX5258 sipxxxxxxxx bell ca user phone gt tag SDocfbb01 453254403 USS OC rk To Bell Demo1l2345 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt tag 344575a8 870a6122 13c4 55013 204e 13ec910e 204 Call ID SDocfbb01 09eee563259466f2de0a5057d0 97d6 a0n8330 CSeq 1028992414 INVITE Via SIP 2 0 UDP 220 20 237 201 5060 branch z 9hG4bKi0m9ki3038alo0l186n0c1 1 Supported sipvc x nortel sipvc 100rel replaces timer User Agent Nortel Networks BCM VoIP Gateway release 46 version 46 51 0 33 P Asserted Identity BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt x nt corr id SDocfbb01 09eee563259466f2de0a5057d0 97d6f a0n8330 Contact lt sip 416XXX1398 10 10 97 34 5060 transport udp gt Session Expires 90 refresher uas Allow INVITE INFO ACK OPTIONS CANCEL BYE NOTIFY PRACK UPDATE RE Content Type application sdp Content Length 241 v 0 o 1950679313 USSOGCISSiLS TN LDA WO hd 7 SA Se c IN IP4 10 10 97 34 t 0 0 m audio 30160 RTP AVP 0 101 c IN IP4 10 10 97 34 a fmtp 101 0 15 a fmtp 18 annexb no a rtpmap 101 telephone event 8000 a fmtp 101 0 15 a sendrecv TD Reviewed Solution amp Interoperability Test Lab Application Notes 38 of 45 SPOC 3 15 2013 2013 Avaya Inc All
25. connect E Refresh ZS Auto refresh SIP Trunking Configuration Administration Resouces A Pubie Private Global setings Weds Parameters Application Reso Preferred Codecs Settings Media Gateways Port Ranges Enable Voice Activity Detection 1 Telephony Resou Available list Selected list Jitter buffer Auto ES jp IP Trunks oa G 729 payload size ms 20 General 8 G 729 F G 711 payload size ms 20 H323 Trunki Fax transport G 711 d ee Force G 711 for 3 1k audio 14 D Telephony Data Services Provide in band ringback Applications 4 m DI gt L Co Mool mit w 54 7 Include ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 22 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 4 2 Codec settings for IP Sets To define the default codec and payload size for IP Sets select Configuration gt Resources gt Telephony Resources Under Internal IP Sets module the default codec and payload size were configured as G 711 uLaw and 20 ms as shown in the following screenshot e Default codec G 711 uLaw e G 711 payload size ms 20 EY Avaya Business Element Ma File Edit View Network Session Tools Help Kg Exit X cut Ba Copy M Paste web Page Vv Validate Device D I Disconnect amp Refresh Z Auto refresh Configuration Administration Welcome Configured Device Dip Switch 3
26. d alarms 5 5 5 Administer Outgoing Call Destination Codes Destination Codes define the dialed prefixes for outgoing calls In the compliance testing a digit 9 was used as an internal access code for outgoing calls over the SIP trunk This access code was configured to be deleted before sending out to Bell Canada To create a Destination Code select Configuration gt Telephony gt Dialing Plan gt Routing Under the Destination Codes tab click Add to create a new route not shown To include dialing plans as described in Section 2 1 multiple Destination Codes e g 90 91 9411 and 9416 were added as shown in the screenshot below Each Destination Code was configured with following paramters e Normal Route 001 created in Section 5 5 4 e Absorbed Length 1 The leading digit 9 will be deleted TD Reviewed Solution amp Interoperability Test Lab Application Notes 27 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM The dialing plan on BCM450 was configured with above Destination Codes to do following e Destination Code 90 To make operator assisted calls by dialing 0 or 0 10 digits It is also be used to make an international call by dialing 011 Country Code Area Code DN Destination Code 91 To make long distance call by dialing 1 10 digits Destination Code 9411 To make directory assisted calls by dialing 411 Destination Code 9416 To make 10 digit local calls with are code 416 by dialing
27. da2b Supported Contact lt sip 1613XXX5279 220 20 237 201 5060 transport udp gt P Asserted Identity lt sip 1613XXX5279 sipxxxxxxxx bell ca user phone gt Allow ACK BYE CANCEL INFO INVITE OPTIONS PRACK REFER NOTIFY UPDATE Accept multipart mixed application media_control xml application sdp Content Type application sdp Content Length 183 v 0 o BroadWorks 6267245 2 IN IP4 220 20 237 201 ga EINER S220202 rc OMe t 0 0 m audio 20386 RTP AVP 0 101 a rtpmap 101 telephone event 8000 a fmtp 101 0 15 a ptime 20 TD Reviewed Solution amp Interoperability Test Lab Application Notes 41 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 6 3 Troubleshooting The BCM Monitor is a builtin troubleshooting tool for BCM450 This section shows how to use this tool to monitor incoming and outgoing calls For further information see the References in Section 8 Use BCM Monitor tool to monitor VoIP Lines for incoming and outgoing calls The following screenshot shows Line001 was used for an active incoming call and Line008 was used for an active outgoing call File Statistics Help BCM Info Media Card Voice Ports IP Devices RTP Sessions UIP Usage Indicators Statistics Line Monitor Active Lines R 1 Line001 Incoming iy Connected Visible lines 7 Line007 Outgoing 3 2235 393 Ide Show all lines including inactive 8 Line008 Outgoing d Connected
28. dvanced tab of the account BellCanada created above In the compliance testing the Advance settings were configured with following values Enable media relay Checked This allows BCM450 to centralize the enterprise RTP traffic before sending to the service provider Support 100rel Checked Bell Canada supports the 100rel signaling as per the RFC 3262 on the SIP Trunk Allow UPDATE Checked Bell Canada supports the UPDATE method on the SIP Trunk Use null IP to hold Checked This allows BCM450 to send null IP to hold the call as per the RFC 2543 Use user phone Checked This allows BCM450 to send URI parameter user phone in the SIP signaling Note Without URI parameter user phone outgoing calls will be rejected by Bell Canada Enable Connected Identity Checked Standard SIP Caps Exchange Checked Session timer BCM450 was configured to refresh the Session Timer every 90 seconds o Session refresh method INVITE o Refresher Local o Session Expires 1800 o Min SE 90 Active call limit 0 This disables the active call limit on BCM450 ITSP association method To header local domain match Basic User Accounts Enable local NAT compensation NAT Pinhole Maintenance Enable media relay V Signaling method None Use maddr in R URI Signaling interval Use maddr in Contact Support 100rel V Allow UPDATE V Session refresh method Use Null IP to hold 7 Refresher Use user phone V Session Expires Force
29. e the SIP signaling from BCM450 o Load balancing Weight Enter 0 to disable the Load balancing on BCM450 o Keep Alive Select OPTIONS in the drop down list This allows BCM450 to send OPTIONS heartbeat on the SIP Trunk for keep alive purpose ger 10 10 97 34 File Edit View Network Session Tools Help KC X Cut E Copy ES Paste Web Page P Validate Device YG Disconnect e Refresh ZE Auto refresh SIP Trunking Administration Welcome Etic private Global Settings Media Parameters IEN System D Administrator Access Resources 9 Application Resour Description Media Gateways Bell Canada SIP Trunking Service Port Ranges EE OO Telephony Resour S IP Trunks J runking 9 Dial Up Interfaces Telephony Data Services E Applications Remote siptrunking bel ca Local cust2 tor vsac bell ca Proxy Address siptrunking bel ca Port Transport UDP Outbound Proxy Table 0 OPTIONS m Done LC 0 LM 0 L__om 18 L__wi 56 TD Reviewed Solution amp Interoperability Test Lab Application Notes r Include ACKed alarms 18 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 3 6 Advance settings The Advance settings define particular parameters for the SIP Trunk to meet the specification of the service provider To configure the Advance settings select A
30. ed for enterprise business customers Customers using Bell Canada SIP Trunking Service with the Avaya SIP enabled enterprise solution are able to place and receive PSTN calls via a broadband WAN connection using SIP protocol This converged network solution is an alternative to traditional PSTN trunks such as analog and or ISDN PRI Bell Canada applies Digest Authentication for outgoing calls from the enterprise It uses challenge response authentication with a 401 Unauthorized responding to each outgoing initial INVITE to Bell Canada The subsequent INVITE from the enterprise provides the Authorization header with a configured user name and password This credential is provided by Bell Canada and configured on BCM450 This call authentication scheme as specified in RFC 3261 provides authentication for the SIP signaling 2 General Test Approach and Test Results DevConnect Compliance testing is conducted jointly by Avaya and DevConnect members The jointly defined test plan focuses on exercising APIs and or standards based interfaces pertinent to the interoperability of the tested products and their functionalities DevConnect Compliance testing is not intended to substitute full product performance or feature testing performed by DevConnect members nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member s solution Bell Canada is a member of the Avaya DevConnect Service Provider P
31. he BCM450 station displayed the VoIP Line00X instead of the original Calling Party Number of PSTN party This is a known behavior of BCM450 with no available resolution at this time This issue has low user impact it is listed here simply as an observation The BCM450 station which forwards an internal call to PSTN displays the improper Calling Party Number Before the forwarded call being answered by PSTN party the BCM450 station displayed Priv OLT gt PSTN Calling Party Number After PSTN party answered the call the display on the BCM450 station changed to VoIP Line00X It should display the Calling Party Number of PSTN party This is a known TD Reviewed Solution amp Interoperability Test Lab Application Notes 4 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM behavior of BCM450 with no available resolution at this time This issue has low user impact it is listed here simply as an observation 3 The BCM450 station which off net conferences an incoming call from PSTN_1 back to PSTN_2 displays the improper Calling Party Number Before the PSTN_2 answered the call the BCM450 station displayed Target LineXXX gt PSTN_2 Calling Party Number After PSTN_2 party answered the call the display on the BCM450 station changed to Target LineX XX VoIP Line00X It should display the Calling Party Number of PSTN parties This is a known behavior of BCM450 with no available
32. ing 27 5 5 5 Administer Outgoing Call Destination COde S ccccccceceeeseceeeeeceeeeeeaeeeeaeeseeeeeseaeeesaeeseneeesaes 27 5 5 6 Administer Outgoing Call SIP Trunk Routing Table 29 5 5 7 Administer Outgoing Call Calling Party Name Delivery ccccccseeeeeeeeceeeeeeeteeeseeeeeeeeeeaes 30 5 5 8 Administer Outgoing Call Calling Party Number Delivery esseessesseesssesseesseessrssersrerssrnennee 32 5 5 9 Administer Outgoing Call Find Me Follow Me 33 5 5 10 Administer Incoming Call Target Lines ccccceecceceeeeeeeeeeeeeeeceeeeeseaeeesaeeseeeeeseaeeesaeeseneeenaes 34 6 Verification and Troubleshooting A 36 GEET Et RE EE 36 6 2 Protocoll Troes aariin iia EAEN AE AEA EA ENEE 36 6 3 TrOuBISSNOOTING reeniros tinei iii eeii EVA EEEIEE E A ER VUA AE VAA EEEE EO OEE 42 EE Let Ee EE 43 8 RECrenCeS iis hg eee el E a eels eye a Me ll a el 44 TD Reviewed Solution amp Interoperability Test Lab Application Notes 2 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 1 Introduction These Application Notes describe the steps to configure Session Initiation Protocol SIP Trunking between Bell Canada SIP Trunking Service Bell Canada and an Avaya SIP enabled enterprise solution The Avaya solution consists of Avaya Business Communication Manager 450 BCM450 Release 6 0 and various Avaya endpoints Bell Canada SIP Trunking Service referenced within these Application Notes is design
33. it A Cut bts Copy amp Paste Web Page J Validate Device YG Disconnect Se Refresh ZS Auto refresh 416 1398 Inactive NNe 4 LC 0 LM Lm LW Include 4CKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 32 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 9 Administer Outgoing Call Find Me Follow Me Find Me Follow Me FMFM is a feature on BCM450 to allow an incoming call to a local phone can be twinned to a PSTN party which may be an cellular extension This section shows addional configuration for Applicaition DNs to support the FMFM calls It is assumed that the basic configuration for FMFM has already been provisioned and will not discuss here To locate the Application DNs which were used for FMFM select Application gt LAN CTE gt Virtual Terminals The Virtual Terminals tab displays a list of Application DNs where used for FMFM call The screenshot below shows DN range 22392 22399 with Application Name FMFM Avaya Business Element Manager 10 10 97 34 o a m File Edit View Network Session Tools Help ER Exit VK cut Bn copy WW Paste Web Page H Validate Device Disconnect Ex Refresh Task Navigation Panel Administration nee Status and Clients Client Privileges Virtual Terminais System Administrator Acces Persistent Terminal ID Application Name Resources Onlin 1 Telephony Data
34. l BlocA as shown in the screenshot below Avaya Business Element Manager 10 10 97 34 j File Edit View Network Session Tools Help opy Paste Web Page wf Validate Device D I Disconnect ZS Refresh f Auto refresh Configuration administration Telephony SCS e Name Control Set 3 Au Global Settings Em d ee No EH R Lines Line002 Line003 Active Physical Lir ged i Target Lines 5 geg Line005 Inactive Lines v aa Line006 Al Lines Line007 Ire m L Co Wp m 0L__W 0 V Include ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 24 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 2 Administer DN Length To configure DN length for BCM450 station select Configuration gt Telephony gt Dialing Plan gt General In the compliance testing DN length for BCM450 stations was set to 5 with Dialing timeout was set to 4 rings as shown in the screenshot below e DN length intercom 5 e Dialing timeout 4 File Edit View Network Session Tools Help KT SM cut Ba copy Paste web Page validate Device YG Disconnect ZS Refresh iP Auto refresh Me mn Lhe wins 4 mm r E E ano ao Include ACKed alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 25 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 5 3 Administe
35. l Canada as shown in the screenshot below File Edit View Network Session Tools Help A exit X cut Bg copy WW Paste Web Page wf Validate Device Y Disconnect Zi Refresh Z Auto refresh Welcome System Administrator Access 0 6 6 BellCanada d Done LC 0 L__M 0 m 17 w 58 V Indude ACKed alarms In the Add Account dialog click No Template and proceed to the next steps not shown TD Reviewed Solution amp Interoperability Test Lab Application Notes 16 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM The SIP Trunk to Bell Canada was configured as the static IP endpoints with the following parameters Name Enter the account name e g BellCanada Description Enter the account description e g BellCanada SIP Trunking Service Template None SIP domain Enter the service provider public SIP domain name e g SIPXXXxxxxx bell ca e Registration required SIP username and Password Leave these fields as blank Bell Canada does not require the Registration on the SIP Trunk Add Account Name BellCanada Description BellCanada SIP Trunking Service Template None SIP domain sip bel ca Registration required SIP username Password 5 3 5 Basic settings The Basic settings define parameters for the SIP Trunk including SIP domains IP address of the far end proxies Registration and OPTIONS keepalive
36. llowing equipment and software were used for the sample configuration provided Component Release Avaya Business Communication Release 6 0 with following patches Manager 450 e BCM450 R600 CORE TELEPHONY 12 e BCM450 R600 SU System 003 201101 e BCM450 R600 SU 2 e BCM450 R100 SU System 012 201003 e BCM450 R100 SU Desktop 006 201006 e BCM450 R100 DSP FIRMWARE 75 Avaya phones e 2004 p2 0604DCN UNIStim e 1140 0625C7M UNIStim e 1120 0624C7M UNIStim e 2007 0621C7G UNIStim e 1220 062AC7M UNIStim e 12050 PC softphone Release 3 2 e Avaya digital phones e Avaya analog phones Component Release Bell Canada SIP Trunking Service TD Reviewed Solution amp Interoperability Test Lab Application Notes 8 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 5 Avaya Business Communication Manager 450 Configuration This section describes the procedure for configuring BCM450 to inter operating with Bell Canada SIP Trunking Service These Application Notes assume that the general installation and configuration of BCM450 have previously been administered For further information see the References in Section 8 5 1 Login to the Avaya Business Element Manager BCM450 configuration is accomplished by using the Avaya Business Element Manager installed on a PC To log on to the Avaya Business Element Manager select Network Elements Enter the credential for User ID nndamin then click Connect
37. n SIP 2 0 401 Unauthorized From BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt tag 34414cd8 870a6122 13c4 55013 19b8 44869384 19b8 To lt sip 1613XXX5279 sipxxxxxxxx bell ca gt tag SDdsnqe99 2020444452 1350676030100 Calas SAS eu VOC OcloslAZ il EE CSeq 1 INVITE Via SIP 2 0 UDP 10 10 97 34 5060 branch z 9hG4bK 19b8 6479a3 cld6dbd WWW Authenticate DIGEST gqop auth nonce BroadWorksXh8hpmutwT11z2y4Bw realm Sipxxxxxxxx bell ca algorit hm MD5 Content Length 0 TD Reviewed Solution amp Interoperability Test Lab Application Notes 39 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM e Outgoing subsequent INVITE with Authorization header to respond to the Digest Authentication INVITE sip 1613XXX5279 sipxxxxxxxx bell ca transport udp SIP 2 0 From BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt tag 34414cd8 870a6122 13c4 55013 19b8 44869384 19b8 To lt sip 1613XXX5279 sipxxxxxxxx bell ca gt Calli y SASL FO OerG 2A ik KoA 50 Sil Soy Cie Ssyeo7 Sil Coys CSeq 2 INVITE Via SIP 2 0 UDP 10 10 97 34 5060 branch z9hG4bK 19b8 6479ea 1208da2b Max Forwards 70 Supported sipvc x nortel sipvc 100rel replaces timer User Agent Nortel Networks BCM VoIP Gateway release 46 version 46 51 0 33 P Asserted Identity BCM450 22264 lt sip 416XXX1398 cust2xxxx xxxx bell ca gt Diversion lt sip 4167751881 cust2xxxx xxxx bell ca gt reason unconditional ROUES Eer 220
38. nstnssrnnsrnnstnnsnnssnnnnnnnsnnnnn nnt Ee TEE E le ln GE E v Reference Gonfig ratio EE EE 4 Equipment and Software Validated csccccececeeeeeeeeeeeeeeceeeeeceaeeesaaeeeeneeseaeeesaaeeeeaaeseeeeeseaeeesaeeneneeeeaes 5 Avaya Business Communication Manager 450 Confguraton 5 1 Login to the Avaya Business Element Manager eu EE 11 5 2 1 Administer Application RESOUICES esineisiin anaa an EAKA ENEA RASEK 11 5 2 2 Administer Media Gateways 12 Eelere Port EE TEE 12 SiS Administerthe S P Rei 13 5 3 1 General IP Trunk eettnges 13 5 3 2 Administer EE 13 5 3 3 Administer Public PO iaoa epia a ARa EE S eA AAEE E E E AE A Aa A 15 5 3 4 Create a Public Account 16 nao Basie SOTUIMNGS eerie a a a A AE EE E R arsed teases 17 e ER AVANCE SOUINGS oeoa i aa a AN AA dae Ea RE Ae depen r a aa tee 19 37 USer ACCOUNT SENINGS veaa ap ee a Ra a iea ae EE Ra AE a EE A 21 5 4 Administer Codec Profile 22 5 4 1 Codec settings for SIP funk 22 5 4 2 Codec settings for IP Get 23 Ba ACGMINiISter Dialing Plan aceea cece pete nee wa cena fan Deed Se cane pte eae SEENEN r Zeien 24 5 5 1 Associate Line Pool to VolP Lines 0 0 ee eececeeeenneeeeeenneeeeeeaaeeeeeeaaeeeseeaaeeeeeeaaeeeeeeaaeeeenenaeeeeneaaes 24 CC Administer DN LO mg tM ssscce exist a aA E E aad Giana I A 25 5 5 3 Administer Public N twork 0 cccceescccceeescceeeeeeeceeeenseceeesaeaeeeeaeaeeesseaeeesneceesesseeeeeesnneeeeeenneaes 26 5 5 4 Administer Outgoing Call Rout
39. p www bell ca enterprise EntPrd_SIP_Trunking page TD Reviewed Solution amp Interoperability Test Lab Application Notes 6 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 3 Reference Configuration Figure 1 illustrates a sample Avaya SIP enabled enterprise solution connected to Bell Canada Vendor Validation Circuit through the Internet For confidentiality and privacy purposes the actual public IP addresses and PSTN routable phone numbers used in the certification testing have been replaced with fictitious parameters throughout the Application Notes For the compliance testing Bell Canada provided the service provider public SIP domain as sipxxxxxxxx bell ca and the enterprise public SIP domain as cust2xxxx xxxx bell ca These public SIP domains will be used for the public SIP traffic between the enterprise and Bell Canada across the public networks with the transport protocol UDP PSTN Pron gt a Bell Canada Mobile Phone SIP Trunking Service 220 20 237 201 Avaya Business Communication Manager 450 yO e G Af Avaya 200X IP phone Avaya 2050 PC softphone Digital phone Analog phones UNIStim UNIStim Fax terminals Figure 1 Avaya IP Telephony Network Connecting to Bell Canada SIP Trunking Service TD Reviewed Solution amp Interoperability Test Lab Application Notes 7 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 4 Equipment and Software Validated The fo
40. phony gt Sets gt Active Sets Under the Line Access tab define Name for an active DN e g 22264 as 22264 as shown in screenshot below Avaya Business Element Manager 10 10 97 34 fo lle File Edit View Network Session Tools Help K Exit SC cut Ba Copy B Paste Web Page Validate Device Disconnect E Refres Task eer Panel Geesse Administration Capabilities and Preferences Restrictions 4 4 Done L Col Molo omolo wn V Include ACKed alarms Continue with the Active Sets settings under the Capabilities and Preferences tab check Auto Called ID to enable the Calling Party Name to display before the call is being answered In the TD Reviewed Solution amp Interoperability Test Lab Application Notes 30 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM the Preferences sub tab select the Business name as Business name 1 and uncheck Send long name as shown in the screenshot below e Business name Business name 1 e Send long name Unchecked This disables the predefined Long name to be sent File Edit View Network Session Tools Help Kr Exit X cut Ba Copy Paste Web Page validate Device D I Disconnect Refresh Auto refresh Configuration System Administrator Access Resources Telephony E Global Settings Inactive DNs AIlDNs e Au Lines Loops OW Scheduled Services A Dialing Plan Ring Groups e A Call Security
41. r Public Network In the compliance testing BCM450 was configured to receive 10 digit incoming calls and use Public Unknown as the call type for outgoing calls To configure the Public Network select Configuration gt Telephony gt Dialing Plan gt Public Network Then configure the Public Receive number length Public network dialing plan and Public network code as following e Public Receive number length 10 e Public network dialing plan Public Unknown e Public network code Leave blank as default Avaya Business Element Manager 10 10 97 34 fo e File Edit View Network Session Tools Help KT cut Ba Copy Paste Web Page wf Validate Device D I Disconnect Pa Refresh ZS Auto refresh Task Navigation Panel Configuration Administration b Telephony m Public Network Settings CR eeng Settings Public Received number length 10 e Public network dialing plan Public Unknown i a o DN Lines Public Auto DN Public network code Dialing Plan Public Network Loops d Public DISA DN Scheduled Services Dialing Plan Public Network DN Lengths Carrier Codes General DNs DN Prefix DN Length Code Prefix Public Network Private Ne Ge L Col wot mp w o V Include ACKed alarms Note The Public network code will affect the Calling Party Number of outgoing calls If specified it will be used in combination with the Pub OLI setting for the phone to form the
42. rkBCM SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved 2013 Avaya Inc All Rights Reserved Avaya and the Avaya Logo are trademarks of Avaya Inc All trademarks identified by and are registered trademarks or trademarks respectively of Avaya Inc All other trademarks are the property of their respective owners The information provided in these Application Notes is subject to change without notice The configurations technical data and recommendations provided in these Application Notes are believed to be accurate and dependable but are presented without express or implied warranty Users are responsible for their application of any products specified in these Application Notes Please e mail any questions or comments pertaining to these Application Notes along with the full title name and filename located in the lower right corner directly to the Avaya DevConnect Program at devconnect avaya com TD Reviewed Solution amp Interoperability Test Lab Application Notes 45 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM
43. rogram The general test approach is to connect a simulated enterprise to the Vendor Validation Circuit through the Internet and exercise the features and functionalities listed in Section Error Reference source not found 2 1 Interoperability Compliance Testing To verify Bell Canada SIP Trunking interoperability the following features and functionalities were covered during the compliance testing e Incoming PSTN calls to various phone types including UNIStim digital and analog telephones at the enterprise All incoming calls from PSTN are routed to the enterprise across the SIP Trunk from the service provider e Outgoing PSTN calls from various phone types including UNIStim digital and analog telephones at the enterprise All outgoing calls to PSTN are routed from the enterprise across the SIP Trunk to the service provider e Incoming and outgoing PSTN calls to from PC 2050 softphones e Dialing plans including local long distance international outgoing toll free operator assisted calls local directory assistance 411 calls etc TD Reviewed Solution amp Interoperability Test Lab Application Notes 3 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM Calling Party Name presentation and Calling Party Name restriction Proper codec negotiation with G 711MU codec Proper media transmission using G 711MU codec Proper early media transmission using G 711MU codec Incoming and outgoing fax over IP using
44. sage Handling CLID Override Display name Override PAI CLID Override PAI Display name Override Contact Override Maddr in Contact Local Domain Override Compensate for NAT SIP Registration Registration 1 TD Reviewed Solution amp Interoperability Test Lab Application Notes 21 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM Notes e The credential was obtained through Bell Canada e The Message Handling fields and SIP Registration were kept blank as default The certification testing does not require either the manipulation on the SIP message headers or the registration 5 4 Administer Codec Profile This section describes the steps for configuring the voice codec on BCM450 to interworking with Bell Canada 5 4 1 Codec settings for SIP Trunk To change the codec settings for SIP Trunk select Configuration gt Resources gt IP Trunks gt SIP Trunk The Media Parameters tab is configured with the following parameters e Selected list G 711 uLaw The certification testing was conducted with only G 711 MU codec Other voice codec e g G 729 or G 723 have not been tested G 711 payload size ms 20 Enable Voice Activity Detection Unchecked Fax transport G 711 The T 38 fax has not been tested Force G 711 for 3 1k audio Checked Avaya Business Element Manager 10 10 97 34 File Edit View Network Session Tools Help A Ext lt Cut les Copy Ce Paste Web Page Validate Device YG Dis
45. the enterprise e g bywdev com e Call signaling port Enter the port for SIP signaling e g 5060 TD Reviewed Solution amp Interoperability Test Lab Application Notes 13 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM RTP Keepalives e Scope RTP This allows BCM450 to send RTP to keep the session active to prevent the termination by Bell Canada if the line is silent In the compliance testing Bell Canada detects the silence on the line if it exceeds the allow duration then the active calls will be disconnected e Initial keepalives Enabled This allows BCM450 to send the initial RTP packet for keepalive purpose e Periodic Timeout 30 The duration of sending out RTP keep alive was set to 30 seconds RFC2833 e Dynamic payload 101 This payload value is preferred by Bell Canada File Edit View Network Session Tools Help dra Cut Ma Copy Paste Web Page f Validate Device Y disconnect e Refresh g Auto refresh Configuration Sie Trunking Welcome Public Prvatel Gobal Settings Media Parameters System Administrator Access Resources Local Domain bvwdev com l Application Besou 3 Keepal ve parameters Media Gateways j 9 Port Ranges ignali Initial keepalives Enabled w Telephony Besou Periodic Timeout 30 IP Trunks o j RFC2833 IC r Dial Up Interfaces Fallback to circuit switched Disabled Dynamic Payload 101
46. this option as unchecked TD Reviewed Solution amp Interoperability Test Lab Application Notes 34 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM e Priv Received Enter the private number assigned to the active DN e g 22264 to receive local system calls or calls over private trunk e Pub Received Enter the public DID number assigned to the active DN e g 416XXX1398 to receive calls over public trunk File Edit View Network Session Tools Help KT A Cut Ba Copy ES Paste Web Page af Validate Device D I Disconnect Se Refresh Ki Auto refresh GJ Sets Name Port Pub OLI Priv OLI ise e 22264 0246 RE C Inactive DNs w Jl Renumber All DNs Lines gt Loops Scheduled Servic Lu Dialing Plan Ring Groups Lu Call Security Hospitality E m L Co Mot mptwci Include ACked alarms TD Reviewed Solution amp Interoperability Test Lab Application Notes 35 of 45 SPOC 3 15 2013 2013 Avaya Inc All Rights Reserved BCSIPTrkBCM 6 Verification and Troubleshooting This section provides verification steps that may be performed in the field to verify that the solution is configured properly This section also provides a list of useful commands that can be used to troubleshoot the solution 6 1 Verification Steps The following activities are made to each test scenario
47. ttings for IP Trunk can be configured by selecting Configuration gt Resources gt IP Trunks gt General Under IP Trunking Settings tab configure the Telephony Settings as shown in the screenshot below e Forward redirected OLI First Redirect In case of multiple call forwards this setting allows the Calling Party Name and Calling Party Number of the call party that firstly redirects the calls e Send name display Checked This setting enables the Calling Party Name and Calling Party Number on the SIP Trunk e Remote capacity MWI Checked e Ignore in band DTMF in RTP Unchecked In the compliance testing Bell Canada supported the out of band DTMF This setting however also allow in band DTMF on the SIP Trunk Avaya Business Element Manager 10 10 97 34 Col Je el File Edit View Network Session Tools Help A Ext Cut Ba Copy E Paste web Page A Validate Device Wi Disconnect Refresh Auto re Task Navigation Panel General Configuration Administration E A Resources E Call Routing Summary IP Trunk Settings Application Resou Media Gateways Port Ranges Telephony Resour jj IP 5 3 2 Administer Global The global settings can be configured by selecting Configuration gt Resources gt IP Trunks gt SIP Trunking Under SIP Trunking tab configure the Global Settings as shown in the screenshot below SIP Settings e Local Domain Enter the private SIP domain for

Avaya Bell Canada SIP Trunking Service with Business Communication Manager 450 Application Note

Contents

Download Pdf Manuals

Related Search

Related Contents