[Home]

Summary:ASTERISK-07557: SIP Interop with Sonus Gateways (npdi=yes causes improper SIP parse)
Reporter:ctaloi (ctaloi)Labels:
Date Opened:2006-08-19 10:36:23Date Closed:2006-08-19 21:14:24
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Interoperability
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) npdi.txt
Description:When a call ingresses from the PSTN over SS7 to a Sonus Gateway Sonus adds npdi=yes in the invite to indiciate a number portability check has been preformed.  This parameter is correct, per RFC, but in my experience Sonus is the only GW to use this.  

It appears Asterisk parses the invite and instead of passing the call to the correct context, it searches for 's' in DOMAIN and returns a 404.

A temp fix was to add this to my extensions.conf:
exten => s,1,Goto(${SIPDOMAIN},s,1)

an excerpt from the attached debug:
/snip
INVITE sip:3155798378;npdi=yes@66.218.0.21 SIP/2.0
/snip
Looking for s in default (domain 3155798378)
/snip

****** STEPS TO REPRODUCE ******

Call Flow:
PSTN [tdm] -> Sonus GW [sip]-> NexTone SBC [sip] -> Asterisk

****** ADDITIONAL INFORMATION ******

This issue is related to bugs:
0007552
0006409
0007208
All of which are closed, I beleive I am using the latest build, which the above bugs indicate this problem has been resolved in.
Comments:By: Joshua C. Colp (jcolp) 2006-08-19 21:14:24

This was fixed in revision 38501 of the 1.2 branch. Please update your copy.