Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Avaya Aura & Unified Communications (http://support.avaya.com/forums/forumdisplay.php?f=2)
-   -   Aura CM/SM 6.1 - SIP tunk with S8300LSP/Branch SM (http://support.avaya.com/forums/showthread.php?t=1568)

stojand 03-19-2012 02:35 AM

Aura CM/SM 6.1 - SIP tunk with S8300LSP/Branch SM
 
Hi,

I have configuration with ME 6.1 (SM 6.1 and CM 6.0.1 with latest SPs) and branch site with G430/S8300D with CM LSP and Branch Session Manager (Survivable Remote Server) and local SBC with SIP trunk.

Is it possible to set SIP trunk between SBC (on branch site) and main CM/procr, and to have SIP trunk running in LSP mode when S8300LSP take over call processing from main CM (in LSP mode)?
I know that H323 trunks work in this way, but I'm not sure about SIP trunks.

I've set sig. group for this SIP trunk with disabled "SIP Enabled LSP" and the configuration for node-names on LSP CM behaves in this way:
nodes for local SBC-Ingate and SM get IP address of BSM (Branch Session Manager). Here are the examples:

Main CM - node-names

IP SM 172.31.10.137
IP bsm 172.31.42.146
IP bsm-lsp 172.31.42.143
IP ingate 172.31.42.111
IP procr 172.31.10.132

LSP CM - node-names

IP SM 172.31.42.146
IP bsm 172.31.42.146
IP bsm-lsp 172.31.42.143
IP ingate 172.31.42.146
IP procr 172.31.10.143

I've tried to enable SIP Enabled LSP feature on sig. group for this SIP trunk but it makes changes on sig goup on LSP side.

Main CM - sig group (CMprocr - SBC/Ingate)

Group Number: 9 Group Type: sip
IMS Enabled? n Transport Method: tcp
Q-SIP? n SIP Enabled LSP? y
IP Video? n Enforce SIPS URI for SRTP? y
Peer Detection Enabled? y Peer Server: Others

Near-end Node Name: procr Far-end Node Name: ingate
Near-end Listen Port: 5060 Far-end Listen Port: 5060
Far-end Network Region: 2
Far-end Domain:



LSP CM - sig group (CMprocr - SBC/Ingate)

Group Number: 9 Group Type: sip
IMS Enabled? n Transport Method: tls
Q-SIP? n SIP Enabled LSP? y
IP Video? n Enforce SIPS URI for SRTP? y
Peer Detection Enabled? y Peer Server: Others

Near-end Node Name: procr Far-end Node Name: procr
Near-end Listen Port: 6001 Far-end Listen Port: 5060
Far-end Network Region: 2
Far-end Domain:


As seen from above, the sig. group for SIP trunk has changed "Far-end Node Name" and "Near/Far-end Listen Ports".

Does anyone have idea about this behaviour?
Any help appreciated.
Dragan

mskinner 03-19-2012 09:14 AM

First of all, the Branch Session Manager does not support SIP trunks today. In theory if your SBCs support multiple IP addresses, then they could connect to the main CM server via Processor Ethernet in sunny day. In rainy day, the SBC at the second location could connect to the Processor Ethernet on the Survivable Remote (LSP). This has never been tested by Avaya, so there are no Application Notes to support this configuration.

stojand 03-20-2012 03:23 AM

I know that BSM doesn't support SIP trunks, and my intention is to use processor interface of main CM in sunny day, and PE of LSP in rainy day. I've already successfully tested SIP alternative routing of SBC.
I've just wondered about this strange behaviour of LSP translation (explained in previous post). Have you any idea about it?
Thanks

aaltvedtob 06-12-2014 05:57 AM

Did you ever manage to get this to work?


All times are GMT -7. The time now is 04:15 AM.