Openscape 4000 Sip Extension

[eniyamath]

Hi all,
I installed X-lite soft phone in my laptop as a sip subscriber for OS4KV7 system
Outgoing calls are working fine but incoming calls from extension as well as from out side are not working.
Can any one help me to resolve out this issue if have an idea.

 

[donb01]

In my experience you have to specify both the incoming and outgoing gateway (server) IP as the board you have built the extension on. You should not have to change ports or anything, and try setting the protocol to UDP Only if that is an option.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Moriendi]

You should run Wireshark on the PC to see if there's an incoming invite from the STMI.

 

[eniyamath]

Dear all,

Thanks for your support

I checked the old thread regarding this issue and found the reason of fault.

I forget to enter the command CHANGE-ZAND:OPTLOAD;

After I send this command in to the system,incoming calls start working.

Thanks again

 

[Moriendi]

So you have configured the SIP subscriber as S0PP. This configuration is obsolete for V7 R2 and onwards, you should configure as UFIP.

Feature support is much improved with the new configuration.

If you are V7 R0/R1, then yes you must use S0PP.

 

[GZgidnick]

Moriendi although they say is S0PP 'obsolete', UFIP has some Digest Authentication incompatibilities with some SIP clients. I have witnessed this with Polycom devices. Only S0PP allowed me to authenticate certain Polycom clients, but again some of them were running very old firmware on them and I had no time to dig into details.

That being said, Unify/4K development is very strict on RFC's as is the case with MoH.

4K would not provide MoH on any clients using "a=sendonly" and "0.0.0.0" method instead of the "a=inactive" method.
The recommended MoH method is "a=inactive" according to RFC 3264 & 6337.
Above renders many many generic SIP clients incompatible with the 4K which unfortunately will not fallback to alternative methods, as the 8K or OsBiz would.

 

[GZgidnick]

eniyamath, don't forget to add the MBCHL attribute in SDAT

 

[donb01]

I'm running V7R2 and all (14) of my SIP is set up as SOPP - that's the way I was taught to do it. Reading this and considering 11 of them are polycom devices that may not be such a bad thing, but I will look into the new stuff to see how it ticks. Never hurts for the old dog to learn new tricks

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[GZgidnick]

dobb01, I'm still running S0PP on v8.1 systems.
However, mostly for Generic SIP clients.

For Unify SIP clients is much more beneficial to run UFIP as many more HFA features have been extended to UFIP but not S0PP.
- Generic SIP clients can't make use of most of this features anyways so S0PP still makes more sense, especially from backward compatibility perspective with older SIP RFC's. S0PP is still an option in RMX and for a good reason to

 

[Moriendi]

S0PP is still an option because to remove it would cause major problems at upgrades but if you report a bug on S0PP the response is going to be try it on UFIP. Going to have to move with the times!! Eventually S0PP SIP will be no more.