cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
755
Views
0
Helpful
1
Replies

asterisk&SPA502G problem with automatic SP answers

asentchernaev
Level 1
Level 1

Asterisk with two different Service Providers, the user phones areSPA502g.

The problem is with "subscriber phone is not swithced on or is out of network coverage" messages, received from SP when the called party in not available. Pointed automatic answer is not allways received on SPA502g phones, but it is allways received on X-Lite soft-phones (undependantly wich SP is used).

When SP1 is used, then SPA phones never "hear" the message (attached "71cisco - fail.pcap" file).

When SP2 is used, then SPA phones allways "hear" it (attached "9cisco - success.pcap" file).

The upgrade of SPA phones to last version didn't help.

Thank you in advance!

Asen

1 Reply 1

Dan Lukes
VIP Alumni
VIP Alumni

Well, PCAP's are usefull, but despite of it, it's hard to understand the issue as I can't listen what you hear during the call progress. The following text assume I understanded the issue correctly.

The 71cisco-fail.pcap show that phone has sent INVITE, the Asterisk responded 183 Session Progress and some inband voice message has been sent to phone. After 0.3s another response, 181 Call is being forwarded, arrived from Asterisk. Followed by 180 RINGING message.

Well, now, you should hear the locally generated ring back tone - not a message from exchange.

It has ben ordered by 180 Ringing message. If you wish to hear a message here, 183 Session Progress message needs to be sent from exchange. That's the difference between 180 and 183 message. The first mean that ringback tone should be generated locally by device, the second mean that progress tone will be sent inband from remote side and local device should play them to the user.

So, it seems that configuration of your Asterisk is wrong.

You can try to set "Sticky 183" configuration option (of SPA phone) to yes.

It's option dedicated to solve interoperability problem misconfigured exchanges like your's. According XLite client - it seems it has simmilar configuration set to "yes" already (or it's not configrable and it is internal default).

But even it will help, it doesn't mean that the Asterisk is not misconfigured. Problems with others SIP clients connected to it are immitent. And not all clients can be configured accordingly to cope with such misconfigured exchange. So the only final solution is to correct Asterisk's configuration.

Of course, if I didn't understood the issue correctly, the conclusions above may be wrong from scratch.