Avaya Communicator - dual registration SIP / H323

[jacks196]

I'm setting up Avaya Communicator in a H323 CM environment on 96xx desk phones - I wish to have dual registration so that an incoming call will ring on both the H323 desk phone and the Avaya Communicator SIP softphone.... If I dial the relevant extension internally from a different H323 desk phone then both the H323 phone and the Communicator softphone ring simultaneously which is exactly what I want, however, if I dial the external DDI number of the extension only the Avaya Communicator softphone rings...

Anybody any ideas, everything appears to be configured correctly in System Manager, my SIP user in SM is the only SIP user configured so I've not any existing config to copy from unfortunately....

Thanks,

Ashley

[derekf]

You're positive it's an H.323 and not a SIP station that you're testing from internally right? Do you have an OPS off pbx station mapping administered for the SIP user? Do you have SIP trunks or TDM? Do you have other SIP users that are working fully, but it's only the dual registration that's behaving like this?

[jacks196]

Hi Derekf,

Yes it is definately a H323 extension I'm dialling from when doing my internal call tests - the only SIP extension we have in the enterprise is my test Avaya Communicator extension (x5469)

I've configured OPS but I'm not 100% convinced I've configued it correctly (see attached file for screenshot).

All trunks are SIP
　
In summary:

x5469 is a fully working H323 extension built in CM

x5469 is a SIP user built in System Manager

If calling from an internal H323 extension both the H323 x5469 and Communicator x5469 endpoints ring simultaneously.

If calling in externally only the SIP x5469 endpoint rings

I can dial internally to H323 endpoints from the SIP x5469

I cannot dial out externally from the SIP x5469 - traceSM reports "Host not trusted" - but that's a seperate issue!
　
　

[derekf]

Is trunk group 1 the SIP trunk to SM? I'm assuming so since internal calls are getting extended to SM and ringing that phone... Is everthing in the same network region? ie. your gateway with the PRI and the phones H.323 and SIP phones? Can you share the traceSM? The "Host not trusted" may be related. How about origination and termination sequences set in the SM profile?

[jacks196]

Hi Derekf,

Yes, trunk 1 is SIP to SM.

The SIP phone and H323 phone are both in the same network region (10).... interestingly none of the Aura kit (ie G450) has a network region defined, although we are using SIP trunks to the outside world so maybe they don't need to be in a network region?..

In the SIP user SM profile we have no origination / termination sequences.

A screenshot of the traceSM is attached with some detail removed - I can PM you with a drill down of any of the messages if you need them.

Thanks for your help.

[derekf]

Everything will be in a network region, but will default to network region 1 if not explicitly defined or defined in the ip-network-map.

You will need an origination and termination application sequence configured for each sip user in their SM profile in SMGR. If they have not available from the drop down, you'll need to do that too under Elements / Session Manager / Application Configuration / Applications and also under Application Sequences.

When you "dial the external DDI number of the extension", are you calling from the H.323 station, or from the PSTN?

Have you tried just going with a full SIP station first instead of dual registration right off the bat?

[jacks196]

Hi Derekf,

Thanks for the information - there are no application sequences configured so I'll see about getting these set up. We've only used SM for routing until now so anything SIP user related is new territory without any existing config.

When we call the external DDI number I'm calling from a mobile, so the call isn't originating from anywhere within the Avaya stack.

Yes, I initially tested with just the SIP station rather than trying to be too ambitious!... everything worked fine using pure SIP, apart from the issue being unable to dial externally (host not trusted).

Thanks for your help, much appreciated.

[derekf]

Here'a link to a guide that may help. It is specific for using remote stations off the SBC, but if you're just trying to do this internally, ignore the sections regarding the SBC configuration. It should touch on all the other configuration items you'd need to do to get SIP stations to work.

https://downloads.avaya.com/css/P8/documents/101027696

[jacks196]

Thanks for your help derekf, it's now working - the problem was because of the missing application sequences in SM. You along with the document have pointed me in the right direction.