Speaking from personal experience; a lot of soft-switch vendors that support SIP-T/SIP-I only support it in a half-baked sort of way. You should always attempt to replicate as much ISUP information as possible using open standard SIP mechanisms. This includes everything from DN information, to LNP information, to Disconnect Reason Codes, ...
It's annoyed me so much that I've started dropping SIP-T/SIP-I for my interconnects and have been reverting to pure SIP. I've found compatibility with a lot of soft-switch vendors is actually improved in this scenario. Joel Gerber Network Specialist Network Operations Eastlink E: [email protected] T: 519.786.1241 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vivek Singla Sent: March-05-13 12:51 PM To: [email protected] Subject: [Sip-implementors] Carrying LNP information in SIP Invite Hi, I am sending local number portability information in the embedded IAM in sip Invite message. But the peer server doesn't seem like my SIP-T message with the embedded IAM. Therefore it doesn't check the LNP information at all. The peer server guy says that I need to send LNP information in the SIP Invite message using R-URI paramaters like npdi, rn etc. My question is that , is it MUST to send the LNP information in SIP Invite and not in embedded IAM. Vivek. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
