SES 3.1.1 call setup problem

[vtec]

Hi everyone,

I have the following setup, a S8300 server running CM3.1.2, SES running 3.1.1. All hotfixes applied. My sip clients consist of the One-X desktop edition, Nokia E60 SIP and on the CM side I have a few 4610 IP Phones.
All seems to be working fine, just as long as you start call from the SIP phone to any phone on the CM (or an outside line). The other way around isn't working at all and also SIP-SIP calling doesn't work.

Any suggestions?

Rgds,

David

 

[rgtrgt]

I had the same problem, there is an issue with SIP sending the wron header information, Avaya knows about the issue & they are writing a patch for it. if i dig up specifics ill post them here.

 

[Rannelator]

We are experiencing the exact same problem.
I have our Avaya field tech engineer researching it.
Haven't heard anything though. Will post if I get info.

Here is the problem and my system info:

I have the SIP server and CM configured "by the book" referencing all the
online docs and the demo videos. I have it partially working:

1. I can make calls to CM from the SIP phones (this includes outside calls).
2. I cannot make calls from CM to the SIP phones.
3. I cannot call other SIP phones.

I get the following error when I run a trace on a call to a SIP phone from CM

16:13:45 dial 3327
16:13:45 seize trunk-group 62 member 12 cid 0x274
16:13:45 Setup digits 3327
16:13:45 Calling Number & Name 7177033321 Rannels, Rand
16:13:45 Proceed trunk-group 62 member 12 cid 0x274
16:13:45 denial event 1166: Unassigned number D1=0xe0011 D2=0x1
16:13:45 idle trunk-group 62 cid 0x274

3321 is my CM extension.
3327 is the SIP extension.
I have 3327 configured in CM as a 4621 and the off-station programming is set OPS to 3327.

System Info:
CM 3.1.2
SES-3.1.1.0-114.0



Randy Rannels
Project Manager
grsCommunication

http://www.grscommunication.com

 

[Rannelator]

BTW: The latest patch for SES 3.1 on the Avaya support site is prior to the release on our server. We have 3.1.114 as opposed to 3.1.018 on the site.

Randy Rannels
Project Manager
grsCommunication

http://www.grscommunication.com

 

[bsmo]

Did you configure the proxy selection route pattern on the locations form ?

 

[Rannelator]

No. I was working with Avaya and they said the proxy
selection route pattern could be blank since in our case
everything is in the same network region.

I found the answer though.
I mis-spelled the domain name on the signaling group form!
DOH!! I must have looked at that form 20 times and never
noticed it. The guy from Avaya had me send him a log file
and he caught it. When I changed it to the correct domain
name it worked!

Lesson Learned: SIP ties everything together via domain
names. Spelling and case are critical. All domain refences
on the SIP server must be lower case, even though you can
use upper case letters in the PBX.
MAKE SURE ALL DOMAIN NAMES ARE IN LOWER CASE.

Randy Rannels
Project Manager
grsCommunication

http://www.grscommunication.com