Ticket #243 (new defect)

Opened 2 months ago

Last modified 4 weeks ago

Setting 'sip_iax_friend=YES' breaks extra charge DNIDs

Reported by: stavros Assigned to: areski
Priority: major Milestone: milestone Version 1.3
Component: AGI Version: Stable 1.3.3 (doudou08)
Keywords: extra charge dnid Cc:

Description

In standard mode if 'sip_iax_friends=YES' then '$A2B->dnid' is overwritten with the received DTMF digits. This causes problems later for the rate engine: extracharge_did will not be correctly applied. For more background see this forum thread.

Change History

08/05/08 15:27:55 changed by asiby

I may be wrong, but I think that these to settings are contradictory and should not be used simultaneously. We have always used 'sip_iax_friends = YES' in a separate context dedicated to SIP/IAX2 peer calls. In that kind of call, extracharge_did does not apply at all, so it make sense not to use it here. Customers will be sending calls from a SIP phone, ATA, a PBX or a Switch.

On the other hand, for calling card applications, extracharge_did applies since customers call in using a DID number. And in that particular case, these is usually no need to let an calling card client reach a peer friend. At least in our case, we don't let calling card users call peer friends.

So unless someone really needs to let a calling card user to reach peer friends, the above separation will help.

Besides, it seems like the 'sip_iax_friends' feature assumes that the call will be made only form a another peer instead of a calling card user.

Cheers



Google