Inter-Session Manager SIP trunks on MES6.2

[agetor]

Hi Guys,

Pardon this basic question but I have tried hard to get some direction and not succeeded yet.

What is the best/recommended way of implementing SIP trunks between two MES6.2 systems at two different locations to achieve the equivalent of H.323 Q-Sig tie trunks. Is it:

• CM1 - CM2 (this works but something seems wrong here to me about the architecture for ver 6.2??? )
• CM1 - SM1 - SM2 - CM2
• CM1 - SM1 - CM2
• other

Or perhaps I got it all horribly wrong? I understand Avaya's move to Session Manager SIP architecture to some extent, but I am yet to see any recommendations or directions on how to implement inter-session manager trunks.


Thanks in advance for all responses.


Regards,


Tony

[agetor]

Well, I am doing some more digging and I am beginning to have a feeling it should be the third option. CM1 and CM2 serve as application servers and provide registration capability to H.323 endpoints at each end.

SM1 and SM2 provide core SIP routing and integration services to enable communication among SIP-enabled entities, gateways, trunks, applications, etc. :

• CM1 ---> SM1 ---> CM2 in one direction and
• CM2 ---> SM2 ---> CM1 in the other direction.....with all necessary entities and entity links configure properly.

Will test this scenario this afternoon ....


Cheers,


Tony

[agetor]

Ok, pieces fallen in place finally. Wondering why it never occurred to me earlier.....
Only needed one session manager - after all, it is THE SIP router!

CM1 <-----> SM1 <-----> CM2 (SM1 could have been SM2).

Been a long day, need some rest ........

Cheers,

T