Programmable Testing for Programmable Telcos, Andreas Granig
0 likes20 views
The document discusses programmable testing for telecom services, emphasizing the importance of both passive and active monitoring to regain control over telecommunications systems. It outlines various testing methodologies, including the use of tools like Kamailio, RTPengine, SIPp, and Baresip for executing and monitoring calls. Additionally, the document provides a sample SIP scenario for active testing and examples of API testing with Curl.
![Ad-Hoc Testing
System
under
Test
sipp
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">
<scenario name="basic-call">
<send>
<![CDATA[
INVITE sip:bob@example.com SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
Max-Forwards: 70
From: "Alice" <sip:alice@example.com>;tag=[call_number]
To: "Bob" <sip:bob@example.com>
Call-ID: [call_id]
CSeq: [cseq] INVITE
Contact: <sip:alice@[local_ip]:[local_port]>
User-Agent: sipp
Content-Type: application/sdp
Content-Length: [len]
v=0
o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip]
s=-
t=0 0
c=IN IP[media_ip_type] [media_ip]
m=audio [media_port] RTP/AVP 8
a=rtpmap:8 PCMA/8000
]]>
</send>
<recv response="100" optional="true">
</recv>
<recv response="180">
</recv>
…
</scenario>](https://image.slidesharecdn.com/programmabletestingforprogrammabletelcos-221111123037-3f50c3ea/85/Programmable-Testing-for-Programmable-Telcos-Andreas-Granig-11-320.jpg)
Programmable Testing for Programmable Telcos, Andreas Granig
- 1. Programmable Testing for Programmable Telcos Andreas Granig <agranig@sipfront.com>
- 2. About me
- 3. Testing? Monitoring? ● Two sides of same coin
- 4. But why?
- 5. Getting back in control!
- 6. 3 Steps ● Passive Monitoring ● Active Monitoring ● Ad-Hoc Testing
- 8. kamailio rtpengine kamailio rtpengine Active Monitoring System under Test Orchestration Aggregation sipp baresip chromium headless kamailio rtpengine Docker Android Emulator
- 9. Remote control ● baresip offers MQTT and HTTP ● sipp offers UDP ● Appium offers Selenium Webdriver ● Kamailio/rtpengine offer MQTT Active Monitoring
- 10. SIP Test Flow Active Monitoring
- 11. Ad-Hoc Testing System under Test sipp <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE scenario SYSTEM "sipp.dtd"> <scenario name="basic-call"> <send> <![CDATA[ INVITE sip:bob@example.com SIP/2.0 Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch] Max-Forwards: 70 From: "Alice" <sip:alice@example.com>;tag=[call_number] To: "Bob" <sip:bob@example.com> Call-ID: [call_id] CSeq: [cseq] INVITE Contact: <sip:alice@[local_ip]:[local_port]> User-Agent: sipp Content-Type: application/sdp Content-Length: [len] v=0 o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip] s=- t=0 0 c=IN IP[media_ip_type] [media_ip] m=audio [media_port] RTP/AVP 8 a=rtpmap:8 PCMA/8000 ]]> </send> <recv response="100" optional="true"> </recv> <recv response="180"> </recv> … </scenario>
- 13. “This is nice, BUT…”
- 14. API Testing curl -X POST “https://app.sipfront.com/api/v2/run” -u “$SIPFRONT_USER:$SIPFRONT_TOKEN” --data-urlencode “test.name=wait-for-call” curl -X POST "https://api.twilio.com/2010-04-01/Accounts/$SID/Calls.json" -u $TWILIO_USER:$TWILIO_TOKEN --data-urlencode "Url=http://demo.twilio.com/docs/voice.xml" --data-urlencode "To=+19991000" --data-urlencode "From=+19992000"
- 15. API Testing curl -X POST “https://app.sipfront.com/api/v2/run” -u “$SIPFRONT_USER:$SIPFRONT_TOKEN” --data-urlencode “test.name=basic-call-a-b”
- 16. THANK YOU